CVE-2026-35672: Initialization of a Resource with an Insecure Default in thorsten phpMyFAQ
phpMyFAQ before 4.1.3 contains an authentication bypass vulnerability in API v4.0 where the default empty api.apiClientToken allows unauthenticated users to create and modify FAQ entries. Attackers can send an empty x-pmf-token header to bypass token validation and inject malicious content via POST endpoints /api/v4.0/faq/create, /api/v4.0/category, and /api/v4.0/question.
AI Analysis
Technical Summary
CVE-2026-35672 describes an authentication bypass vulnerability in phpMyFAQ prior to version 4.1.3. The issue arises because the default api.apiClientToken is empty, enabling attackers to bypass token validation by sending an empty x-pmf-token header. This allows unauthorized creation and modification of FAQ entries through the API endpoints /api/v4.0/faq/create, /api/v4.0/category, and /api/v4.0/question. The vulnerability affects the integrity of the application but does not impact confidentiality or availability.
Potential Impact
The vulnerability allows unauthenticated attackers to inject or modify FAQ content, compromising the integrity of the phpMyFAQ system. There is no direct impact on confidentiality or availability reported. No known exploits in the wild have been documented at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability is fixed in phpMyFAQ version 4.1.3, upgrading to this or a later version is recommended once available. Until then, restricting access to the API endpoints or implementing additional access controls may reduce risk.
CVE-2026-35672: Initialization of a Resource with an Insecure Default in thorsten phpMyFAQ
Description
phpMyFAQ before 4.1.3 contains an authentication bypass vulnerability in API v4.0 where the default empty api.apiClientToken allows unauthenticated users to create and modify FAQ entries. Attackers can send an empty x-pmf-token header to bypass token validation and inject malicious content via POST endpoints /api/v4.0/faq/create, /api/v4.0/category, and /api/v4.0/question.
CVSS v3.1
Score 7.5high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-35672 describes an authentication bypass vulnerability in phpMyFAQ prior to version 4.1.3. The issue arises because the default api.apiClientToken is empty, enabling attackers to bypass token validation by sending an empty x-pmf-token header. This allows unauthorized creation and modification of FAQ entries through the API endpoints /api/v4.0/faq/create, /api/v4.0/category, and /api/v4.0/question. The vulnerability affects the integrity of the application but does not impact confidentiality or availability.
Potential Impact
The vulnerability allows unauthenticated attackers to inject or modify FAQ content, compromising the integrity of the phpMyFAQ system. There is no direct impact on confidentiality or availability reported. No known exploits in the wild have been documented at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability is fixed in phpMyFAQ version 4.1.3, upgrading to this or a later version is recommended once available. Until then, restricting access to the API endpoints or implementing additional access controls may reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-04-04T12:32:50.476Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a186052e29bf47b500b4201
Added to database: 5/28/2026, 3:33:38 PM
Last enriched: 5/28/2026, 3:50:34 PM
Last updated: 5/29/2026, 8:21:41 AM
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.