Content modification via omitted API permission checks
Published Jun 18, 2026 · Updated Jun 18, 2026
Missing authorization in phpMyFAQ before 4.1.4 allows remote authenticated users to create or alter FAQ content through four API endpoints. The category, FAQ, and question write methods validate a shared API key but omit userHasPermission checks for the requested operation. Any API token holder can therefore create categories, FAQs, or questions and update FAQ entries regardless of the holder's assigned role.
Summary
What happened
Missing authorization in phpMyFAQ before 4.1.4 allows remote authenticated users to create or alter FAQ content through four API endpoints. The category, FAQ, and question write methods validate a shared API key but omit userHasPermission checks for the requested operation. Any API token holder can therefore create categories, FAQs, or questions and update FAQ entries regardless of the holder's assigned role.
The record
- CVE
- CVE-2026-49205
- Published
- Jun 18, 2026
- Updated
- Jun 18, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2026CVE publishedPublication date reported by the CVE source.
- Jun 18, 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=< 4.1.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
No public exploit references are available in this record.
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