dbcve.org
GravApplication · Getgrav

CVE-2026-29924

HIGH · 7.6 CVSS v3.1 Published 2026-03-30
Fix available
A fix is available. Upgrade to 1.8.0 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Grav CMS v1.7.x and before is vulnerable to XML External Entity (XXE) through the SVG file upload functionality in the admin panel and File Manager plugin.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Grav CMS v1.7.x and earlier contains an XML External Entity (XXE) vulnerability in the SVG file upload functionality accessible through the admin panel and File Manager plugin. Attackers can upload malicious SVG files containing external entity references to read local files from the server, perform SSRF attacks, or cause denial of service.

MitigationDisable external entity processing in the XML parser used for SVG files, implement strict SVG content validation, or restrict SVG upload permissions to trusted admin users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GravApplication
Affected:< 1.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grav CMS version
    Check the version.php or VERSION file in the Grav installation root directory, or look at the admin dashboard footer which displays the version number
    Affected if Installed version is 1.7.x or any version earlier than 1.8.0
  2. Confirm admin panel access
    Verify whether the /admin or /grav-admin endpoint is accessible and functional in your environment
    Affected if The admin panel is accessible and users with upload permissions exist
  3. Check File Manager plugin status
    Navigate to the Plugins section in the admin panel or inspect the /user/plugins/ directory for the filesystem or file-manager plugin folder and its enabled.yaml setting
    Affected if File Manager or filesystem plugin is installed and enabled with upload capability
  4. Verify XML parser handles external entities
    Test by attempting to upload a minimal SVG file containing an XXE payload (DOCTYPE with external entity) to see if the parser resolves it, or inspect the XML processing configuration in the admin or plugin code
    Affected if The XML parser processes external entities in uploaded SVG files without blocking them

You are affected if you are running Grav CMS version 1.7.x or earlier AND have the admin panel accessible with File Manager plugin enabled and the XML parser processes external entities in SVG uploads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.8.0 or later
Fixed in 1.8.0
Interim mitigation

Disable external entity processing in the XML parser used for SVG files, implement strict SVG content validation, or restrict SVG upload permissions to trusted admin users only.

Recommended fix Moderate confidence

Grav CMS 1.8.0

  1. 1. Backup your Grav CMS installation and database before proceeding with any upgrade.
  2. 2. Navigate to the official Grav CMS download page or your server's Grav installation directory.
  3. 3. Download Grav CMS version 1.8.0 or later from the official source.
  4. 4. Replace the existing Grav core files with the new version, preserving your user configuration and content files.
  5. 5. If using the File Manager plugin, ensure it is also updated to a compatible version.
  6. 6. Clear any caching systems (system cache, CDN caches) after the upgrade.
  7. 7. Test the SVG file upload functionality in the admin panel to confirm the vulnerability is remediated.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grav Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29924 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29924 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data