# CVE-2026-112296: FlyCms through commit edfdf724 Default Super Administrator Credentials

> Unauthenticated attackers can log in using default super administrator credentials to gain full control of the FlyCms web application.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 19 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-6phq-6cxr-q574

## What is CVE-2026-112296?

CVE-2026-112296 is a critical vulnerability in sunkaifei FlyCms, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FlyCms through commit edfdf724 contains a default credentials vulnerability that allows unauthenticated remote attackers to gain super administrator access via the flycms account with password admin123. Attackers can log in through POST /api/auth/login, solving only the image captcha, to obtain full control of site content, users and configuration.

Weakness: CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2026-112296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112296 is a critical vulnerability in sunkaifei FlyCms, published on 19 Oct 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-112296 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-112296/ (Markdown: https://insights.sbomify.com/CVE-2026-112296/index.md)
```

## Sources

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

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