Quick answers
- Is CVE-2026-92381 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92381 being exploited in the wild.
- How severe is CVE-2026-92381?
- Low severity, with a CVSS score of 3.5, published 16 September 2026.
- Which products and versions are affected?
- PbootCMS up to 3.2.22.
- Is there a fix for CVE-2026-92381?
- 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-92381 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92381?
- Check whether you run PbootCMS 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 cross-site scripting (XSS) vulnerability in the template rendering component. The root cause is an asymmetric encode/decode design: article titles are HTML-encoded on input (via htmlspecialchars) and stored in the database, but on frontend display they are decoded (via htmlspecialchars_decode) and output directly to templates without secondary filtering. Unlike the content field which calls filter_html(), the title field bypasses all output sanitization. An attacker with content editing permissions (standard editor role) can inject arbitrary HTML/JavaScript into the title field; when the article is displayed on detail pages, list pages, or the homepage, the payload executes in all visitors' browsers. The vulnerability affects PbootCMS up to at least 3.2.22 and is confirmed exploitable with public proof-of-concept code available.
Affected products
- PbootCMS PbootCMS up to 3.2.22
Timeline
- 2026-08-19: disclosed: GitHub issue opened reporting stored XSS vulnerability
- 2026-09-16: advisory: CVE-2026-92381 published