CVE-2026-130348 json
phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Category ACL Bypass
published yesterday modified 14h ago also EUVD-2026-126799 , GHSA-5cmj-fjjf-3v8h , GHSA-8qg6-v67x-pv5p
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository thorsten/phpMyFAQ. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authorization vulnerability that exposes restricted and inactive category metadata to unauthenticated visitors. Attackers can enumerate category IDs via /category/{id}/{slug}.html or query /api/v4.0/categories to read names, descriptions, images and FAQ counts of restricted categories.
Patch / fix
- thorsten phpMyFAQ 4.1.12, 4.2.0-RC.2
Is CVE-2026-130348 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 14h ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-17).
Exploits and checks
- github.com https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-5cmj-fjjf-3v8h referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- thorsten phpMyFAQ
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
github.com
/thorsten/phpMyFAQ/commit/baf88a067a873c11074690ce547a3221a3f280cd
patch
-
github.com
/thorsten/phpMyFAQ/commit/6049d3e9798ea0292ca27a21c29d8d7e8f3428c0
patch
-
github.com
/thorsten/phpMyFAQ/security/advisories/GHSA-5cmj-fjjf-3v8h
vendor-advisory, exploit, advisory
-
github.com
/thorsten/phpMyFAQ/security/advisories/GHSA-8qg6-v67x-pv5p
vendor-advisory, advisory
-
github.com
/thorsten/phpMyFAQ/releases/tag/4.1.12
release-notes
-
github.com
/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
release-notes
-
vulncheck.com
/advisories/phpmyfaq-4.1.0-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-category-acl-bypass
third-party-advisory
Sources
- CVE List CVE-2026-130348
- NVD CVE-2026-130348
- Maintainer advisory GHSA-5cmj-fjjf-3v8h
- Maintainer advisory GHSA-8qg6-v67x-pv5p
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of thorsten/phpMyFAQ published their own advisory on GitHub. Reviewed sources take precedence over it.