# CVE-2026-95653: Concrete CMS Community Store before 2.7.8 Predictable Digital Download Token

> Unauthenticated attackers can predict download tokens to retrieve digital goods purchased by other customers in Concrete CMS Community Store.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-4m3m-829w-5q37

## What is CVE-2026-95653?

CVE-2026-95653 is a high-severity vulnerability in concretecms-community-store community_store, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Concrete CMS Community Store before 2.7.8 derives digital product download tokens from order creation timestamps instead of random values, making tokens predictable. Unauthenticated attackers can enumerate sequential order and file identifiers to calculate valid download tokens and retrieve digital goods purchased by other customers.

Weakness: CWE-340 (Generation of Predictable Numbers or Identifiers)

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


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

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

## Is CVE-2026-95653 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95653 is a high-severity vulnerability in concretecms-community-store community_store, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-95653 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-95653/ (Markdown: https://insights.sbomify.com/CVE-2026-95653/index.md)
```

## Sources

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

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