# CVE-2026-111888: phpMyFAQ 4.0.0 before 4.1.9 Incorrect Authorization via news update API

> Delegated admins can modify public news items by exploiting incorrect authorization checks in the news update API.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-287v-6c6j-x9f7, GHSA-j2g3-mcv7-r3f2

## What is CVE-2026-111888?

CVE-2026-111888 is a medium-severity missing authorization vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

phpMyFAQ from 4.0.0 before 4.1.9 contains an incorrect authorization vulnerability that allows delegated admins lacking the editnews right to modify news by calling PUT /admin/api/news/update, which checks NEWS_DELETE instead of NEWS_EDIT. Attackers holding addnews and delnews can read the update-news CSRF token from their own cookie and rewrite any news item's header, body, author, link and active flag shown on the public front page.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-111888 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111888 is a medium-severity missing authorization vulnerability in thorsten phpMyFAQ, published on 17 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111888 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-111888/ (Markdown: https://insights.sbomify.com/CVE-2026-111888/index.md)
```

## Sources

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

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