# CVE-2026-130345: phpMyFAQ 4.2.0-alpha before 4.2.0-RC.2 Information Disclosure via Web Push Broadcast


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/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-234w-v3h8-xch7

## What is CVE-2026-130345?

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

### Official description

phpMyFAQ 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability that allows authenticated frontend users to receive restricted FAQ titles by subscribing to Web Push notifications. When editors publish user/group-restricted FAQs, WebPushService::sendToAll() delivers the question, FAQ id, category, and slugified URL to every subscriber, bypassing the FAQ ACL.

Weakness: CWE-862 (Missing Authorization)

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

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 | 4.2.0-RC.2 |

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

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

## Is CVE-2026-130345 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- 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-130345/ (Markdown: https://insights.sbomify.com/CVE-2026-130345/index.md)
```

## Sources

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

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