# CVE-2026-116216: MacCMS v10 through 2026.1000.4056 Comment Impersonation via user_id Mass Assignment


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/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-9f7c-9m42-3x6j

## What is CVE-2026-116216?

CVE-2026-116216 is a medium-severity vulnerability in maccmspro maccms10, published on 26 Oct 2026. 

### Official description

MacCMS v10 through 2026.1000.4056 contains a mass assignment vulnerability in index/Comment::saveData() that allows unauthenticated attackers to set arbitrary mac_comment columns including user_id. Attackers can submit anonymous comments with a crafted user_id parameter to attribute them to any registered member, displaying that member's avatar and impersonating them.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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


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

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

## Is CVE-2026-116216 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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