Quick answers
- Is CVE-2026-11982 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11982 being exploited in the wild.
- How severe is CVE-2026-11982?
- Informational severity, with a CVSS score of 5.1, published 18 June 2026.
- Which products and versions are affected?
- Grav Admin Panel Plugin 2.0.0-rc.14; Grav API Plugin 1.7.52.
- Is there a fix for CVE-2026-11982?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-11982 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-11982?
- Check whether you run Grav Admin Panel Plugin or Grav API Plugin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stored cross-site scripting (XSS) vulnerability exists in Grav 2.0.0-rc.9 with Admin2 2.0.0-rc.14. The root cause is located in the `validateChangedFields()` function within the Admin2/API partial page save path (specifically the PATCH /pages endpoint). While the system performed standard validation, it failed to execute `Validation::checkSafety()`, allowing `Security::detectXss()` to be bypassed. A non-superadmin editor can persist malicious event-handler payloads (e.g., img tags with onerror attributes) in page Markdown. These payloads execute when rendered on the frontend for any viewer, including administrators. A fix has been committed to the grav-plugin-api repository to enforce XSS safety checks during partial-field validation.
Affected products
- Grav grav-plugin-api 1.7.52
- Grav Grav CMS 2.0.0-rc.9
- Grav Admin2 plugin 2.0.0-rc.14
Timeline
- 2026-06-18: disclosed
- 2026-06-18: advisory