CVE-2026-26351
Received Received - Intake
Stored XSS in GetSimpleCMS Components Allows Persistent Admin Hijack

Publication date: 2026-02-24

Last updated on: 2026-02-26

Assigner: VulnCheck

Description
GetSimpleCMS Community Edition (CE) version 3.3.16 contains a stored cross-site scripting (XSS) vulnerability in the Theme to Components functionality within components.php. User-supplied input provided to the "slug" field of a component is stored without proper output encoding. While other fields are sanitized using safe_slash_html(), the slug parameter is written to XML and later rendered in the administrative interface without sanitation, resulting in persistent execution of arbitrary JavaScript. An authenticated administrator can inject malicious script content that executes whenever the affected Components page is viewed by any authenticated user, enabling session hijacking, unauthorized administrative actions, and persistent compromise of the CMS administrative interface.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-24
Last Modified
2026-02-26
Generated
2026-05-07
AI Q&A
2026-02-25
EPSS Evaluated
2026-05-05
NVD
CVE-2026-26351
EUVD
EUVD-2026-8572
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
getsimple-ce getsimple_cms From 3.3.16 (inc) to 3.3.22 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a stored cross-site scripting (XSS) issue in GetSimpleCMS Community Edition version 3.3.16, specifically in the Theme to Components functionality within the components.php file.

An authenticated administrator can supply malicious input to the "slug" field of a component. Unlike other fields that are sanitized, the slug parameter is stored without proper output encoding and later rendered in the administrative interface without sanitation.

This results in persistent execution of arbitrary JavaScript code whenever the affected Components page is viewed by any authenticated user.


How can this vulnerability impact me? :

The vulnerability allows an authenticated administrator to inject malicious scripts that execute persistently in the CMS administrative interface.

  • Session hijacking of authenticated users.
  • Unauthorized administrative actions performed via injected scripts.
  • Persistent compromise of the CMS administrative interface, potentially leading to further exploitation.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart