phpMyFAQ: Public API endpoints expose emails and invisible questions
thorsten phpMyFAQ
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| phpmyfaq/phpmyfaq Packagist |
|
|
| thorsten/phpmyfaq Packagist |
|
|
thorsten phpMyFAQ
| Product | Affected | Fixed in |
|---|---|---|
| phpmyfaq/phpmyfaq Packagist |
|
|
| thorsten/phpmyfaq Packagist |
|
|
phpMyFAQ is an open source FAQ web application. In versions 4.0.16 and below, multiple public API endpoints improperly expose sensitive user information due to insufficient access controls. The OpenQuestionController::list() endpoint calls Question::getAll() with showAll=true by default, returning records marked as non-public (isVisible=false) along with user email addresses, with similar exposures present in comment, news, and FAQ APIs. This information disclosure vulnerability could enable attackers to harvest email addresses for phishing campaigns or access content that was explicitly marked as private. This issue has been fixed in version 4.0.17.
From the CVE record · GitHub_M
In phpMyFAQ versions before 4.0.17, insufficient access controls in public API endpoints expose user email addresses and content marked non-public. Attackers can retrieve this information through the affected question, comment, news, and FAQ APIs.
Teams running phpMyFAQ through the Packagist packages phpmyfaq/phpmyfaq or thorsten/phpmyfaq should check installations below version 4.0.17.