dbcve.org
XML External Entity (XXE)Weakness · CWE-611

CVE-2026-56701

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 before 2.0.0-beta.2 contains an XML external entity injection vulnerability in SVG file upload processing that allows authenticated attackers to read arbitrary files. The application uses simplexml_load_string without disabling external entity loading, enabling attackers to inject XXE payloads via malicious SVG files to exfiltrate sensitive data.

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 · high confidence

Grav CMS before 2.0.0-beta.2 is vulnerable to XML external entity injection (XXE) in its SVG file upload functionality. The application parses uploaded SVG files using PHP's simplexml_load_string() without disabling external entity loading, allowing authenticated attackers to upload malicious SVG files containing XXE payloads to read arbitrary files from the server filesystem.

MitigationUpgrade to Grav 2.0.0-beta.2 or later which addresses this vulnerability. As a workaround, ensure XML parsing in SVG upload handlers explicitly disables external entity loading using libxml_disable_entity_loader() or equivalent before calling simplexml_load_string().

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

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
None
Availability
None

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

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 file or composer.json in the Grav installation root directory to determine the installed version
    Affected if The installed version is any release before 2.0.0-beta.2
  2. Verify SVG upload functionality is accessible
    Confirm that the file upload feature accepts SVG files - typically via the Admin plugin Media page or direct API endpoint at /admin/media.json
    Affected if SVG files can be uploaded to the system by authenticated users
  3. Check XML parser configuration in upload handlers
    Locate the PHP code handling SVG uploads and inspect the simplexml_load_string() calls - verify whether libxml_disable_entity_loader(true) or equivalent is called before parsing
    Affected if SVG upload handlers use simplexml_load_string() without disabling external entity loading first
  4. Confirm user authentication is enabled
    Verify that the Grav Admin plugin is installed and user accounts exist - the attack requires an authenticated session
    Affected if Admin authentication is enabled and users can access the media upload feature

A system is affected if running Grav CMS version before 2.0.0-beta.2 with SVG upload capability accessible to authenticated users, and the upload handler does not disable external entity loading before parsing uploaded SVG files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Grav 2.0.0-beta.2 or later which addresses this vulnerability. As a workaround, ensure XML parsing in SVG upload handlers explicitly disables external entity loading using libxml_disable_entity_loader() or equivalent before calling simplexml_load_string().

Recommended fix Moderate confidence

Grav CMS 2.0.0-beta.2 or later stable release

  1. 1. Backup your current Grav installation and database before proceeding
  2. 2. Navigate to your Grav installation directory
  3. 3. Run the Grav updater to upgrade to version 2.0.0-beta.2 or later using: composer update grav/cms --with-all-dependencies
  4. 4. Alternatively, download the latest Grav version from the official GitHub repository at github.com/getgrav/grav
  5. 5. After upgrade, clear the cache by deleting the cache/ directory
  6. 6. Verify the upgrade was successful by checking the Grav admin panel version number
Caveat Beta versions may have unstable features; test thoroughly in staging before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56701 — 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-56701 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