Stored XSS via unsanitized component slug
Published Feb 24, 2026 · Updated Feb 24, 2026
Stored XSS in components.php in GetSimple CMS Community Edition before 3.3.22 allows remote authenticated users to execute JavaScript. The component-save path writes the submitted slug to XML without sanitation and later inserts it into markup on the administrative Components page. Administrator access is required to store the payload, and execution occurs when an authenticated user views that page, exposing that user's session and administrative actions.
Summary
What happened
Stored XSS in components.php in GetSimple CMS Community Edition before 3.3.22 allows remote authenticated users to execute JavaScript. The component-save path writes the submitted slug to XML without sanitation and later inserts it into markup on the administrative Components page. Administrator access is required to store the payload, and execution occurs when an authenticated user views that page, exposing that user's session and administrative actions.
The record
- CVE
- CVE-2026-26351
- Published
- Feb 24, 2026
- Updated
- Feb 24, 2026
- Vendor
- GetSimpleCMS-CE
- Product
- GetSimple CMS Community Edition
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Feb 24, 2026CVE publishedPublication date reported by the CVE source.
- Feb 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.3.16
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo