Answer in brief
CVE-2026-35672 records a High severity (CVSS 8.7) vulnerability in phpMyFAQ - Authentication Bypass via Empty API Token. The current sources do not mark it as known exploited. The current feed maps thorsten/phpmyfaq (composer), phpmyfaq/phpmyfaq (composer), thorsten/phpMyFAQ (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps thorsten/phpmyfaq (composer), phpmyfaq/phpmyfaq (composer), thorsten/phpMyFAQ (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| thorsten/phpmyfaqcomposer | <=4.1.2 | 4.1.3 |
| phpmyfaq/phpmyfaqcomposer | <=4.1.2 | 4.1.3 |
| thorsten/phpMyFAQgeneric | >=0 <4.1.3 | 4.1.3 |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.