phpMyFAQ - Authentication Bypass via Empty API Token

published 2026-05-20 5 mo ago modified 2026-11-08 19 h ago also EUVD-2026-32903 , GHSA-gp95-j463-vv28

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits: 0; none known

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.

Patch / fix

fixed in 3

packagist thorsten/phpmyfaq 4.1.3
packagist phpmyfaq/phpmyfaq 4.1.3
thorsten phpMyFAQ 4.1.3

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 5 mo ago (2026-05-28)

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-gp95-j463-vv28 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA	4.0	8.7	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA	4.0	8.7	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem	package	affected	fixed in
packagist	thorsten/phpmyfaq	<4.1.3	4.1.3
packagist	phpmyfaq/phpmyfaq	<4.1.3	4.1.3

Affected products

thorsten phpMyFAQ

Classification

Weakness

CWE-1188 Initialization of a Resource with an Insecure Default

References

github.com /thorsten/phpMyFAQ/security/advisories/GHSA-gp95-j463-vv28
vendor-advisory, exploit, web
vulncheck.com /advisories/phpmyfaq-authentication-bypass-via-empty-api-token
third-party-advisory, web
nvd.nist.gov /vuln/detail/CVE-2026-35672
advisory
github.com /thorsten/phpMyFAQ
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary