CVE-2026-49205: CWE-862: Missing Authorization in thorsten phpMyFAQ
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.
AI Analysis
Technical Summary
phpMyFAQ is an open source FAQ web application. Versions before 4.1.4 suffer from a missing authorization vulnerability (CWE-862) in the API CategoryController and other write endpoints. While a previous CVE (CVE-2026-24421) fixed authorization in the BackupController by adding user permission checks, four other write endpoints (POST /api/v4.0/category, POST /api/v4.0/faq, PUT /api/v4.0/faq, POST /api/v4.0/question) only verify a shared API key token without validating the individual user's role permissions. This allows unauthorized users with the API key to perform write operations. The vulnerability is fixed in version 4.1.4.
Potential Impact
An attacker with access to the shared API key can perform unauthorized write operations on categories, FAQs, and questions via the affected API endpoints. This could lead to unauthorized content creation or modification. Confidentiality, integrity, and availability impacts are limited to the ability to create or update content without proper authorization. There is no indication of privilege escalation or system compromise beyond the application data.
Mitigation Recommendations
Upgrade phpMyFAQ to version 4.1.4 or later, where this missing authorization issue is fixed by enforcing user permission checks on all relevant API endpoints. Until upgraded, restrict access to the shared API key to trusted users only to minimize risk.
CVE-2026-49205: CWE-862: Missing Authorization in thorsten phpMyFAQ
Description
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.
CVSS v3.1
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
phpMyFAQ is an open source FAQ web application. Versions before 4.1.4 suffer from a missing authorization vulnerability (CWE-862) in the API CategoryController and other write endpoints. While a previous CVE (CVE-2026-24421) fixed authorization in the BackupController by adding user permission checks, four other write endpoints (POST /api/v4.0/category, POST /api/v4.0/faq, PUT /api/v4.0/faq, POST /api/v4.0/question) only verify a shared API key token without validating the individual user's role permissions. This allows unauthorized users with the API key to perform write operations. The vulnerability is fixed in version 4.1.4.
Potential Impact
An attacker with access to the shared API key can perform unauthorized write operations on categories, FAQs, and questions via the affected API endpoints. This could lead to unauthorized content creation or modification. Confidentiality, integrity, and availability impacts are limited to the ability to create or update content without proper authorization. There is no indication of privilege escalation or system compromise beyond the application data.
Mitigation Recommendations
Upgrade phpMyFAQ to version 4.1.4 or later, where this missing authorization issue is fixed by enforcing user permission checks on all relevant API endpoints. Until upgraded, restrict access to the shared API key to trusted users only to minimize risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-28T03:42:34.340Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a346bc9f198dc38c1a1cd9a
Added to database: 06/18/2026, 22:06:01 UTC
Last enriched: 06/26/2026, 13:11:45 UTC
Last updated: 08/02/2026, 19:17:59 UTC
Views: 63
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.