phpMyFAQ - Authentication Bypass via Empty API Token
thorsten phpMyFAQ
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| thorsten/phpmyfaq Packagist |
|
|
| phpmyfaq/phpmyfaq Packagist |
|
|
thorsten phpMyFAQ
| Product | Affected | Fixed in |
|---|---|---|
| thorsten/phpmyfaq Packagist |
|
|
| phpmyfaq/phpmyfaq Packagist |
|
|
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.
From the CVE record · VulnCheck
phpMyFAQ before 4.1.3 has an authentication bypass in API v4.0 when api.apiClientToken is left empty by default. An unauthenticated attacker can send an empty x-pmf-token header to create or modify FAQ entries and inject malicious content through API POST endpoints.
Anyone running thorsten/phpmyfaq or phpmyfaq/phpmyfaq versions before 4.1.3 should check their installation.