# CVE-2026-93659: Concrete CMS Community Store before 2.7.8 Stored XSS

> Attackers can inject scripts into order fields to execute code in admin sessions, enabling account takeover and data theft.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-9rr2-pvrh-g3pm

## What is CVE-2026-93659?

CVE-2026-93659 is a high-severity cross-site scripting vulnerability in concretecms-community-store community_store, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Concrete CMS Community Store before 2.7.8 renders customer-supplied order fields without HTML escaping in checkout and admin views. Unauthenticated attackers can store script payloads in billing name, email, or phone fields that execute in authenticated manager sessions to create rogue accounts or exfiltrate data.

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

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


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

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

## Is CVE-2026-93659 being exploited?

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

Public exploit code:

- Stored XSS in Concrete CMS Community Store leads to admin dashboard takeover (github_poc): https://github.com/prince325/CVE-2026-93659-writeup

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93659 is a high-severity cross-site scripting vulnerability in concretecms-community-store community_store, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-93659 in the wild and no public exploit code.

Affected product: concretecms-community-store community_store. 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-93659/ (Markdown: https://insights.sbomify.com/CVE-2026-93659/index.md)
```

## Sources

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

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