VulnerabilityPublished 5 May 2026Updated 23 Sep 2026

CVE-2026-56701: getgrav/grav · Grav is Vulnerable to XXE via SVG Upload

Affects getgrav/gravSource GCVE Database

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.0.0-beta.2 when convenient.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.0.0-beta.2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade getgrav/grav to 2.0.0-beta.2.

Affected software

Product	Affected	Fixed in
Packagistgetgrav/grav	Affected <2.0.0-beta.2	Fixed in 2.0.0-beta.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security fix is available and has been applied in Grav CMS version 2.0.0-beta.2 and the updated dom-sanitizer library. The fix strips DOCTYPE and ENTITY declarations from SVG files before XML parsing and disables external entity loading, preventing XXE exploitation. Users should upgrade to Grav 2.0.0-beta.2 or later and ensure the updated dom-sanitizer library is in use. No additional mitigation actions are required once patched.

Description

Grav CMS versions prior to 2.0.0-beta.2 are vulnerable to an XML External Entity (XXE) injection via SVG file uploads. Authenticated attackers with admin panel access can upload malicious SVG files that exploit improper XML parsing to read arbitrary server files, perform SSRF, or cause denial of service. The vulnerability arises from using simplexml_load_string without disabling external entity loading. A fix has been applied in Grav 2.0.0-beta.2 and the associated SVG sanitizer library to strip dangerous XML declarations and disable external entity processing.

Impact

An authenticated attacker with admin panel access can exploit this vulnerability to read arbitrary files on the server, including sensitive configuration and credential files, potentially leading to credential disclosure and system information leakage. The attacker can also perform server-side request forgery (SSRF) to access internal services and cause denial of service through recursive entity expansion attacks.

Summary

Grav CMS versions before 2.0.0-beta.2 improperly process uploaded SVG files using simplexml_load_string without disabling external entity loading, allowing authenticated attackers to perform XXE attacks. This enables reading sensitive files such as /etc/passwd, user account YAML files, system configuration, and environment secrets. The vulnerability also allows SSRF and potential denial of service via billion laughs attacks. The issue is fixed by stripping DOCTYPE and ENTITY declarations before parsing and using libxml flags (LIBXML_NONET, LIBXML_NOERROR, LIBXML_NOWARNING) and disabling entity loaders on PHP < 8. The fix is implemented in Grav core 2.0.0-beta.2 and the dom-sanitizer library.

CWE-611Improper Restriction of XML External Entity Reference (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Implementation · System Configuration
Many XML parsers and validators can be configured to disable external entity expansion.
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.2 (opens in a new tab)
Attack patterns
Data Serialization External Entities Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Sep 2026, 07:00 UTC

WeaknessesCWE-611

Technical details

References

Community reviews

Related threats