Unauthenticated content modification via empty API token
Published May 28, 2026 · Updated May 28, 2026
Authentication bypass in phpMyFAQ before 4.1.3 allows remote attackers to modify FAQ content through API v4.0 with an empty token. DefaultDataSeeder initializes api.apiClientToken to an empty string, and AbstractController::hasValidToken accepts an empty x-pmf-token header as an exact match. The REST API is enabled by default; affected installations permit unauthenticated creation or modification of FAQ entries, categories, and questions.
Summary
What happened
Authentication bypass in phpMyFAQ before 4.1.3 allows remote attackers to modify FAQ content through API v4.0 with an empty token. DefaultDataSeeder initializes api.apiClientToken to an empty string, and AbstractController::hasValidToken accepts an empty x-pmf-token header as an exact match. The REST API is enabled by default; affected installations permit unauthenticated creation or modification of FAQ entries, categories, and questions.
The record
- CVE
- CVE-2026-35672
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-1188, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.1.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Empty-token REST API proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo