High severity · published May 28, 2026
CVE-2026-35672
phpMyFAQ - Authentication Bypass via Empty API Token
7.5
CVSS
0.5%
EPSS
No
On KEV
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 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 41% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PH
phpMyFAQ · thorsten
before 4.1.3 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-35672
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-35672
github.com
https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-gp95-j463-vv28
www.vulncheck.com
https://www.vulncheck.com/advisories/phpmyfaq-authentication-bypass-via-empty-api-token
More from phpMyFAQ
9.8
CVE-2026-111911
phpMyFAQ 4.0.0 before 4.1.9 Authentication Bypass via WebAuthn Credential Injection
9.8
CVE-2026-46364
phpMyFAQ - SQL Injection via User-Agent Header in BuiltinCaptcha
9.4
CVE-2026-66398
phpMyFAQ before 4.1.6 Remote Code Execution via Configuration API
9.1
CVE-2026-45010
phpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check Endpoint
8.8
CVE-2026-75918
phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File