# CVE-2026-130377: phpMyFAQ 4.2.0-alpha.2 before 4.2.0-RC.2 Authorization Bypass via FAQ Delete API


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-g6v9-9w5x-p4pv

## What is CVE-2026-130377?

CVE-2026-130377 is a medium-severity vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 

### Official description

phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability in DELETE /admin/api/faq/delete that lets language-scoped FAQ_DELETE admins bypass their language scope. Attackers can submit a faqId with an in-scope faqLanguage lacking a translation to wipe shared ACL, tags, votes, comments, and attachments of other translations.

Weakness: CWE-863 (Incorrect Authorization)

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

1 open source package ship an affected version, including thorsten/phpmyfaq.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `thorsten/phpmyfaq` | Packagist | `pkg:composer/thorsten/phpmyfaq` | From 4.2.0-alpha.2 | 4.2.0-RC.2 |

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

Upgrade thorsten/phpmyfaq to 4.2.0-RC.2 or later.

## Is CVE-2026-130377 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130377 is a medium-severity vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130377 exists.

Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected from 4.2.0-alpha.2; fixed in 4.2.0-RC.2

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

## Sources

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

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