# CVE-2026-130367: phpMyFAQ through 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Authorization Bypass via FAQ Copy/Translate


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

## What is CVE-2026-130367?

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

### Official description

phpMyFAQ through 4.1.12 and from 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the admin FAQ copy and translate pages, which check only global FAQ_ADD or FAQ_TRANSLATE rights. Authenticated add-only or category-scoped editors can open any FAQ to read drafts, ACL-restricted records, private notes, and author e-mail addresses.

Weakness: CWE-863 (Incorrect Authorization)

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

2 open source packages ship an affected version, including thorsten/phpmyfaq.


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

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

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

## Is CVE-2026-130367 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130367 is a medium-severity vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130367 in the wild and no public exploit code.

Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected all versions up to 4.1.12; no fix listed
- thorsten/phpmyfaq (Packagist): affected from 4.2.0-alpha; 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-130367/ (Markdown: https://insights.sbomify.com/CVE-2026-130367/index.md)
```

## Sources

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

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