CVE-2026-116215 MacCMS v10 through 2026.1000.4056 Race Condition via Card Redemption
Low 2.3
Published
Updated
Check this codebase for CVE-2026-116215 and fix it if it is affected.
What it is: CVE-2026-116215 is a low-severity vulnerability in maccmspro maccms10, published on 26 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-116215 in the wild and no public exploit code.
Affected product: maccmspro maccms10. 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-116215/ (Markdown: https://insights.sbomify.com/CVE-2026-116215/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116215?
CVE-2026-116215 is a low-severity vulnerability in maccmspro maccms10, published on 26 Oct 2026.
Official description
MacCMS v10 through 2026.1000.4056 contains a race condition vulnerability in Card::useData() that allows authenticated members to redeem one recharge card multiple times via the user/buy endpoint. Attackers can send many concurrent flag=card requests that pass the non-locking card read before it is marked used, inflating user_points to buy VIP upgrades and paid content.
Weakness: CWE-362
Which versions are affected by CVE-2026-116215?
How do I fix CVE-2026-116215?
No fix has been published for CVE-2026-116215 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116215 being exploited?
There is no known exploitation of CVE-2026-116215 in the wild and no public exploit code.
Sources
Also known as GHSA-m463-2mww-7vjr.