# CVE-2026-26351: GetSimpleCMS-CE < 3.3.22 Stored XSS via components.php

> Authenticated administrators can inject persistent JavaScript via the component slug field, leading to session hijacking and administrative interface compromise.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-95f7-vm92-8gpx, GHSA-98hq-gxg8-fchj

## What is CVE-2026-26351?

CVE-2026-26351 is a medium-severity cross-site scripting vulnerability in GetSimpleCMS-CE, published on 24 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

GetSimpleCMS Community Edition (CE) versions prior to 3.3.22 (3.3.16 tested) 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-26351?

It affects 1 product.


Products: Getsimple-Ce Getsimple Cms.

## How do I fix CVE-2026-26351?

No fix has been published for CVE-2026-26351 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26351 being exploited?

There is no known exploitation of CVE-2026-26351 in the wild and no public exploit code.

## Other vulnerabilities in GetSimpleCMS-CE

- [CVE-2024-55085](https://insights.sbomify.com/CVE-2024-55085/): Code injection in n/a (critical 9.8)
- [CVE-2026-28495](https://insights.sbomify.com/CVE-2026-28495/): GetSimple CMS has CSRF to Remote Code Execution via Arbitrary PHP Write in gsconfig.php (critical 9.7)
- [CVE-2026-27202](https://insights.sbomify.com/CVE-2026-27202/): GetSimple CMS: Uploaded Files (feature) Arbitrary File Read Vulnerability (high 8.8)
- [CVE-2024-55088](https://insights.sbomify.com/CVE-2024-55088/): Server-side request forgery in n/a (high 8.8)
- [CVE-2026-27161](https://insights.sbomify.com/CVE-2026-27161/): Unauthenticated Information Disclosure via .htaccess Reliance in Sensitive Directories (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26351 and fix it if it is affected.

What it is: CVE-2026-26351 is a medium-severity cross-site scripting vulnerability in GetSimpleCMS-CE, published on 24 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-26351 in the wild and no public exploit code.

Affected product: GetSimpleCMS-CE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26351/ (Markdown: https://insights.sbomify.com/CVE-2026-26351/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26351
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26351
- OSV: https://osv.dev/vulnerability/CVE-2026-26351

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26351/
Summaries are generated and may contain mistakes; the official description above is the record.