CVE-2026-130348 · Runtime
NO FIX YET · SEE WHAT TO DO
phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 fails to check authorization on restricted and inactive FAQ categories. Unauthenticated visitors can list category IDs and read category names, descriptions, images and FAQ counts through the category page and the categories API.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running phpMyFAQ 4.1.0 to before 4.1.12, or 4.2.0-alpha to before 4.2.0-RC.2, where some FAQ categories are restricted or inactive. Sites on the fixed versions, or with no restricted categories to protect, are not exposed to the metadata leak.
Not affected if fixed-version, no-restricted-categories
Who cares php, phpmyfaq, self-hosted
VERSION file of the install./api/v4.0/categories on the public site and see whether restricted category names come back without logging in.4.1.12 for the 4.1 line4.2.0-RC.2 for the 4.2 linephpMyFAQ 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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
This page as .md · .json · 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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.