# CVE-2026-111901: phpMyFAQ 4.2.0-alpha before 4.2.0-beta Unauthenticated DoS via API Pagination

> Unauthenticated attackers can crash the phpMyFAQ server by sending concurrent requests to API endpoints that exhaust system resources.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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:** 17 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-45x8-rjq5-9jpp, GHSA-m42f-6p37-2c79

## What is CVE-2026-111901?

CVE-2026-111901 is a high-severity denial of service vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

phpMyFAQ 4.2.0-alpha before 4.2.0-beta contains an uncontrolled resource consumption vulnerability in the unauthenticated faqs and search API endpoints. Attackers can send concurrent GET requests that load and process all database records into PHP memory, exhausting CPU and memory to crash the server.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-111901 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111901 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111901 is a high-severity denial of service vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111901 exists.

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-111901/ (Markdown: https://insights.sbomify.com/CVE-2026-111901/index.md)
```

## Sources

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

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