CVE-2026-130349
Deferred Deferred - Pending Action

phpMyFAQ Incorrect Authorization Bypass via REST Endpoints

Vulnerability report for CVE-2026-130349, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
phpmyfaq phpmyfaq From 4.2.0-alpha.2 (inc) to 4.2.0-RC.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in phpMyFAQ versions 4.2.0-alpha.2 through 4.2.0-RC.2 allows editors with restricted category or language permissions to bypass those restrictions via public REST API write endpoints. Attackers with a scoped API token can use endpoints like PUT faq/update, POST faq/create, and POST category to modify published FAQs or create root categories outside their intended scope.

Detection Guidance

Check phpMyFAQ REST API logs for unauthorized PUT faq/update, POST faq/create, or POST category requests. Monitor for unexpected modifications to FAQs or creation of root categories outside assigned scopes. Review API tokens for shared usage across restricted editors.

Impact Analysis

If exploited, this vulnerability could allow unauthorized users to rewrite published FAQs or create new categories outside their designated scope. This compromises data integrity by enabling modifications to live content that should be restricted. Attackers need an authenticated user with scoped permissions and knowledge of the shared API token.

Compliance Impact

This vulnerability could impact compliance by allowing unauthorized modifications to sensitive data, potentially violating integrity and access control requirements in GDPR and HIPAA. Unauthorized changes to FAQs or categories may lead to data corruption or exposure of restricted information.

Mitigation Strategies

Upgrade phpMyFAQ to version 4.2.0-RC.2 or later. Review and restrict API token usage to prevent shared access. Audit existing FAQs and categories for unauthorized changes. Implement additional access controls on public REST endpoints.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130349. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...