CVE-2026-130349 · Package
NO FIX YET · SEE WHAT TO DO
phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 lets editors restricted to certain categories or languages bypass those limits through public REST write endpoints. An attacker with a scoped editor right and the shared API token can rewrite published FAQs and create root categories outside their scope.
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 in the 4.2.0-alpha.2 to 4.2.0-RC.2 range that use scoped editor roles and the REST API with the shared API token. Installations without restricted editors or without the REST API exposed are less exposed. The sources do not describe further conditions.
Not affected if api-disabled, no-scoped-editors
Who cares phpmyfaq, rest-api, self-hosted
4.2.0-RC.2.4.2.0-RC.2 or later (from the sources' stated range).phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability that allows category- or language-restricted editors to bypass scoped rights via public REST write endpoints. Attackers with a scoped right and the shared API token can use PUT faq/update, POST faq/create, and POST category to rewrite published FAQs and create root categories outside their scope.
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.