# CVE-2026-111908: phpMyFAQ 4.0.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta BOLA in FAQ Update via REST API

> Authenticated users with edit permissions can modify restricted FAQs they cannot view, bypassing moderation and changing publication states.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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:** 17 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-cwqc-qp2c-47mg, GHSA-j3px-r7cr-r26r

## What is CVE-2026-111908?

CVE-2026-111908 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 4.0.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta contains a broken object-level authorization vulnerability in the PUT /api/v3.1/faq/update endpoint, which checks only the global edit_faq permission and does not verify access to the target FAQ. Authenticated users with edit_faq permission can supply the ID of a restricted FAQ they cannot view to modify its content, bypass moderation, and change its publication state.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111908 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111908 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111908 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-111908/ (Markdown: https://insights.sbomify.com/CVE-2026-111908/index.md)
```

## Sources

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

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