# CVE-2026-112295: FlyCms through commit edfdf724 Mass Assignment via /ucenter/account_update

> Authenticated users can exploit mass assignment to modify protected account fields, potentially taking over other users' accounts.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-pp6m-j5rg-683m

## What is CVE-2026-112295?

CVE-2026-112295 is a medium-severity vulnerability in sunkaifei FlyCms, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FlyCms through commit edfdf724 contains a mass assignment vulnerability that allows authenticated users to overwrite protected account columns by submitting extra User bean fields to /ucenter/account_update. Attackers can change their review status, rename themselves, or duplicate another account's username, email or mobile to break that victim's login.

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

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


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

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

## Is CVE-2026-112295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112295 is a medium-severity vulnerability in sunkaifei FlyCms, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112295 in the wild and no public exploit code.

Affected product: sunkaifei FlyCms. 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-112295/ (Markdown: https://insights.sbomify.com/CVE-2026-112295/index.md)
```

## Sources

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

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