# CVE-2026-111909: phpMyFAQ before 4.1.9 Missing Authorization Allows Superadmin Deletion via deleteUser API

> Authenticated users with delete permissions can delete superadmin accounts, removing administrative access and accountability in phpMyFAQ.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/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:** 17 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-2jrh-wx9p-9fp9, GHSA-7j43-ww55-pm3g

## What is CVE-2026-111909?

CVE-2026-111909 is a high-severity missing authorization vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

phpMyFAQ before 4.1.9 contains a missing authorization vulnerability in the deleteUser() API that allows authenticated non-superadmin users with delete_user permission to delete superadmin accounts. Attackers can send a DELETE request to /admin/api/user/delete with a superadmin's userId other than 1, removing administrative access and accountability.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-111909 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111909 is a high-severity missing authorization vulnerability in thorsten phpMyFAQ, published on 17 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-111909 in the wild and no public exploit code.

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

## Sources

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

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