Quick answers
- Is CVE-2026-81926 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81926 being exploited in the wild.
- How severe is CVE-2026-81926?
- Medium severity, with a CVSS score of 6.1, published 15 September 2026.
- Which products and versions are affected?
- Concrete CMS 9.4.0 through 9.5.2.
- Is there a fix for CVE-2026-81926?
- 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-81926 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-81926?
- Check whether you run Concrete CMS 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
This is a stored/reflected cross-site scripting (XSS) vulnerability in the page location panel's duplicate-path confirmation dialog. The root cause is improper output encoding: the panel's check endpoint returns a user-supplied page path unmodified in its JSON response, and client-side JavaScript then inserts this value directly into the dialog as raw HTML without escaping. An authenticated editor with sufficient privileges can craft a malicious page path containing script tags (e.g., <script>...</script>) that will execute in the browser of any other user who views the duplicate-path confirmation. No special preconditions are needed beyond authentication and editor-level permissions. An attacker can execute arbitrary JavaScript in the victim's authenticated session context, potentially leading to credential theft, unauthorized content modification, or further lateral movement within the CMS. Patches addressing output encoding are available in versions after 9.5.2.
Affected products
- Concrete CMS Concrete CMS 9.4.0 through 9.5.2
Timeline
- 2026-09-15: disclosed
- other: CVE-2026-81926 assigned