Categories
CVE-2026-100670 high CVSS 8.8

Vulnerability in Grav CMS (CVE-2026-100670)

Summary

Vulnerability in Grav CMS (CVE-2026-100670). Successful exploitation can lead to full system takeover. Exploitable via access.admin.super. Mitigation: upgrade to 2.0.25 or later.

Original description

The description as published by the source.

Grav CMS 2.0.14 through 2.0.24 contains a privilege escalation vulnerability in the group and account blueprints. The access map is gated by a security@: admin.super guard that is resolved by the field's exact path, so a submitted flat dot-notation key such as access.admin.super (instead of the nested access[admin][super]) matches no blueprint rule, survives BlueprintSchema::filterArray() and flattening, and is written by FlexObject::update() via setNestedProperty(), which splits on . and reconstructs the nested value. An authenticated backend operator using the flex accounts backend who holds admin.users but not admin.super can therefore grant admin.super to their own account or to a group they belong to and escalate to full super-admin, gaining control over configuration, plugin and theme installation, the file manager, and all accounts. Fixed in 2.0.25, which drops any dotted key whose ancestor path is disabled or marked validate.ignore.

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-100670 has been found in Grav CMS.
Attackers can target a specific entry point like access.admin.super over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Grav CMS to 2.0.25 or later.
If unsure, ask your IT team or search "Grav CMS CVE-2026-100670" on the vendor's site.

CVE-2026-100670 (Grav CMS) — CWE-639 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: access.admin.super
Patched: 2.0.25 — 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-639) exists in Grav CMS. Attackers reach the vulnerable code path via access.admin.super.

📍 Affected scope

Check the vendor advisory for the affected versions of Grav CMS. Attack surface: access.admin.super.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.0.25.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Grav CMS を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade Grav CMS to 2.0.25

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

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

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

References

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