thorsten phpMyFAQ up to 4.1.3 Public API /api/v4 hasValidToken userHasPermission authorization

Summaryinfo

A vulnerability marked as problematic has been reported in thorsten phpMyFAQ up to 4.1.3. Affected by this issue is the function hasValidToken of the file /api/v4 of the component Public API. Performing a manipulation of the argument userHasPermission results in authorization. This vulnerability is known as CVE-2026-49205. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in thorsten phpMyFAQ up to 4.1.3. This affects the function hasValidToken of the file /api/v4 of the component Public API. The manipulation of the argument userHasPermission with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. The summary by CVE is:

phpMyFAQ is an open source FAQ web application. Versions prior to 4.1.4 have Missing Authorization in the API CategoryController. CVE-2026-24421 addressed this in the BackupController by adding: $this->userHasPermission(PermissionType::BACKUP). The same fix was not applied to 4 other write endpoints in the public API. All 4 only call $this->hasValidToken() — which checks a shared API key header, rather than the individual user's role permissions. The following APIs are affected: POST /api/v4.0/category (CategoryController::create), POST /api/v4.0/faq (FaqController::create), PUT /api/v4.0/faq (FaqController::update), and POST /api/v4.0/question (QuestionController::create). This issue has been fixed in version 4.1.4.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-49205 since 05/28/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.

Upgrading to version 4.1.4 eliminates this vulnerability. Applying the patch d5c195b1ecf5dc30fb825d7eb50d22481c24cb07 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Vendor

• thorsten

Name

• phpMyFAQ

Version

• 4.1.0
• 4.1.1
• 4.1.2
• 4.1.3

License

• open-source

Website

• Product: https://github.com/thorsten/phpMyFAQ/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion