Categories
CVE-2026-76839 medium CVSS 6.5

Vulnerability in getgrav/grav (CVE-2026-76839)

Summary

Vulnerability in getgrav/grav (CVE-2026-76839). Confidential information can be exposed externally. Exploitable via offsetget. Mitigation: upgrade to 2.0.16 or later.

Original description

The description as published by the source.

Summary

system/config/security.yaml's Twig sandbox policy allow-lists offsetget and
offsetexists for Grav\Common\User\Interfaces\UserInterface. The concrete
Grav\Common\User\DataUser\User class does not filter which fields offsetGet()
returns, so any sandboxed template with access to a User object can read
hashed_password, secret (2FA seed), and twofa_secret directly, bypassing the
redaction Grav's own code applies everywhere else.

The core evidence, from Grav's own code

system/src/Grav/Common/User/DataUser/User.php:

/**
 * {@inheritdoc}
 * Override to filter out sensitive fields like password hashes
 */
public function jsonSerialize(): array
{
    $items = parent::jsonSerialize();

    // Security: Remove sensitive fields that should never be exposed to frontend
    unset($items['hashed_password']);
    unset($items['secret']);         // 2FA secret
    unset($items['twofa_secret']);   // Alternative 2FA field name

    return $items;
}

public function offsetGet($offset)
{
    $value = parent::offsetGet($offset);
    // only special-cases 'authorized', nothing else -- no redaction
    return $value;
}

system/config/security.yaml:

- class: 'Grav\Common\User\Interfaces\UserInterface'
  methods: 'authorize, authorized, authenticated, username, fullname, email, language, offsetget, offsetexists'

This is the same vulnerability shape as two already-fixed issues in this file
(GHSA-j274-39qw-32c9 and GHSA-mc5q-6hpj-rp7j --…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-76839 has been found in getgrav/grav.
Attackers can target a specific entry point like offsetget over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade getgrav/grav to 2.0.16 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-76839" on the vendor's site.

CVE-2026-76839 (getgrav/grav) — CWE-522 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: offsetget / offsetexists / User / hashed_password
Patched: 2.0.16 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-522) exists in getgrav/grav. Attackers reach the vulnerable code path via offsetget.

📍 Affected scope

Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: offsetget / offsetexists / User / hashed_password.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.0.16.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'getgrav/grav' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'getgrav/grav' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で getgrav/grav を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade getgrav/grav to 2.0.16

    ステージング環境で 2.0.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer getgrav/grav
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.16"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details