Skip to main content
Menu
CVEs

Grav Plugin Form stored XSS via unsanitized SVG file uploads

Affects grav-plugin-form 9.1.39 and earlier on Grav 1.7 or 2.x served by Apache, with a public form whose file field accepts any file type. Fixed in 9.1.40.

CVE-2026-134250Published November 21, 2026, updated

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 9.1.40
Who is exposed
Specific setups only

Summary

The Grav Form plugin has a stored cross-site scripting flaw in its file upload handling. It cleans SVG files only when the final extension is .svg, so a file such as drawing.svg.foo can carry script. An anonymous attacker can upload such a file remotely through public upload forms, and the script runs in an administrator's session when that administrator opens the file, which can allow creating a super-admin account on Grav with Admin2.

Written by a model

Original description

Grav Form plugin 1.1.0 before 9.1.40 contains a stored cross-site scripting vulnerability in Form::uploadFiles(), which sanitizes SVG only when a file's last extension is .svg and accepts markup under unrecognized extensions. Anonymous attackers can upload files like drawing.svg.foo through public any-type upload forms, running script in an administrator's session when opened, enabling super-admin creation on Grav 2.x with Admin2.

Who should check

Teams running grav-plugin-form 9.1.39 or earlier on Grav 1.7 or 2.x, served by Apache, with public file-upload forms that accept any file type; Grav 2.x sites using Admin2 are most at risk.

“grav-plugin-form 9.1.39 and earlier, on Grav 1.7 and 2.x, served by Apache”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    grav-plugin-form 9.1.39 and earlier Running on Grav 1.7 or 2.x Served by Apache (likely Caddy for the markup case); nginx and IIS following Grav's shipped configs are not affected A public form whose file field accepts any file type (accept: ['*'] or a rule matching application/octet-stream) Uploaded file is saved in the web-served page folder (default self@ destination)
  2. Upgrade to a fixed version: 9.1.40.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134250 (Grav Form Plugin 1.1.0 before 9.1.40 Stored XSS via Unsanitized File Uploads), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134250 (entry last updated 2026-11-21):
Affected:
- getgrav grav-plugin-form: from 1.1.0, fixed in 9.1.40
Fixed versions: 9.1.40.
Conditions (all must be true for the bug to be hit):
- grav-plugin-form 9.1.39 and earlier (source: https://github.com/getgrav/grav/security/advisories/GHSA-2vpw-p335-mmmp)
- Running on Grav 1.7 or 2.x (source: https://github.com/getgrav/grav/security/advisories/GHSA-2vpw-p335-mmmp)
- Served by Apache (likely Caddy for the markup case); nginx and IIS following Grav's shipped configs are not affected (source: https://github.com/getgrav/grav/security/advisories/GHSA-2vpw-p335-mmmp)
- A public form whose file field accepts any file type (accept: ['*'] or a rule matching application/octet-stream) (source: https://github.com/getgrav/grav/security/advisories/GHSA-2vpw-p335-mmmp)
- Uploaded file is saved in the web-served page folder (default self@ destination) (source: https://github.com/getgrav/grav/security/advisories/GHSA-2vpw-p335-mmmp)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-134250 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134250 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/getgrav/grav/security/advisories/GHSA-2vpw-p335-mmmp
- https://www.vulncheck.com/advisories/grav-form-plugin-1.1.0-before-9.1.40-stored-xss-via-unsanitized-file-uploads
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134250
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134250"}.

Affected versions

cve.now Index

21Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · getgrav/grav · Advisory GHSA-2vpw-p335-mmmp
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134250
RecordNVD · CVE-2026-134250
Other links 1
Linkvulncheck.com · advisories/grav-form-plugin-1.1.0-before-9.1.40-stored-xss-via-unsanitized-file-uploads

Questions about CVE-2026-134250

Is CVE-2026-134250 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Uploaded files are saved in the web-served page folder without sanitization, so a file can carry script that an anonymous visitor plants for any session that opens it, including a super-admin's. On Grav 2.x with Admin2, that script can read the administrator's API token and act as that administrator.

Source: github.com

Which versions are affected by CVE-2026-134250?

grav-plugin-form: from 1.1.0 before 9.1.40.

Source: cve.now feed data

Am I affected, and how do I check?

The plugin range is grav-plugin-form 1.1.0 up to 9.1.40, and the conditions cover 9.1.39 and earlier on Grav 1.7 or 2.x served by Apache, with a public form whose file field accepts any file type and saves uploads to the default self@ destination. Check the installed plugin version in the Grav admin plugins list, the Grav version, the web server type, and the file field's accept setting in the form blueprint.

Source: github.com

How do I fix CVE-2026-134250?

Upgrade grav-plugin-form to 9.1.40 or later. The facts do not name vendor patch ids.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.