# CVE-2026-116214: MacCMS v10 before 2026.1000.4054 Account Takeover via Unbound Password Recovery Code


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-x697-8hfh-c2rc

## What is CVE-2026-116214?

CVE-2026-116214 is a critical vulnerability in maccmspro maccms10, published on 26 Oct 2026. 

### Official description

MacCMS v10 before 2026.1000.4054 contains an authentication bypass vulnerability that allows unauthenticated attackers to reset any member's password because check_msg() never compares msg_to. Attackers can request a recovery code to their own mailbox via user/findpass_msg, then submit it to user/findpass_reset with the victim's email or phone to take over the account.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2026-116214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116214 is a critical vulnerability in maccmspro maccms10, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116214 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-116214/ (Markdown: https://insights.sbomify.com/CVE-2026-116214/index.md)
```

## Sources

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

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