Summary
phpMyFAQ: Missing userHasPermission() in 4 API write endpoints (CVE-2026-24421 Incomplete Fix)
Missing Authorization in API CategoryController, CVE-2026-24421 fixed BackupController by adding userHasPermission(PermissionType::BACKUP). The same fix was NOT applied to 4 other write endpoints in the public API. All 4 only call hasValidToken() (shared API key) but never call userHasPermission(), allowing any API token holder to perform admin operations regardless of their user permissions.
CVE-2026-24421 fixed 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, NOT the individual user's role permissions.
Affected Endpoints
src/phpMyFAQ/Controller/Api/CategoryController.php → create() POST /api/v4.0/category
Missing: userHasPermission(PermissionType::CATEGORY_ADD)
Any API token holder can create categories regardless of user role.src/phpMyFAQ/Controller/Api/FaqController.php → create() POST /api/v4.0/faq
Missing: userHasPermission(PermissionType::FAQ_ADD)
Any API token holder can create FAQ entries regardless of user role.src/phpMyFAQ/Controller/Api/FaqController.php → update() PUT /api/v4.0/faq
Missing: userHasPermission(PermissionType::FAQ_EDIT)
Any API token holder can update any FAQ entry regardless of user role.src/phpMyFAQ/Controller/Api/QuestionController.php → create() POST /api/v4.0/question
Missing: permission check
Any API token holder can create questions regardless of user role.
Root Cause
All 4 methods only call:
$this->hasValidToken(); ← shared API key, not per-user
The fixed BackupController correctly calls:
$this->userHasPermission(PermissionType::BACKUP);
PermissionType::CATEGORY_ADD, FAQ_ADD, FAQ_EDIT all exist in src/phpMyFAQ/Enums/PermissionType.php, they just are not being used.
Reporter
CONTACT
Santhoshini Ganta
Github:@santhoshinipayload
Email: [email protected]
LinkedIn: http://linkedin.com/in/santhoshini-g-1440621ba
Impact
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
CVE-2026-49205 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.1.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Add userHasPermission() before the logic in each method:
// CategoryController.create()
$this->userHasPermission(PermissionType::CATEGORY_ADD);
// FaqController.create()
$this->userHasPermission(PermissionType::FAQ_ADD);
// FaqController.update()
$this->userHasPermission(PermissionType::FAQ_EDIT);
Frequently Asked Questions
- What is CVE-2026-49205? CVE-2026-49205 is a medium-severity missing authorization vulnerability in thorsten/phpmyfaq (composer), affecting versions < 4.1.4. It is fixed in 4.1.4. The application does not perform an authorization check before performing a sensitive operation.
- How severe is CVE-2026-49205? CVE-2026-49205 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-49205?
thorsten/phpmyfaq(composer) (versions < 4.1.4)phpmyfaq/phpmyfaq(composer) (versions < 4.1.4)
- Is there a fix for CVE-2026-49205? Yes. CVE-2026-49205 is fixed in 4.1.4. Upgrade to this version or later.
- Is CVE-2026-49205 exploitable, and should I be worried? Whether CVE-2026-49205 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-49205 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-49205?
- Upgrade
thorsten/phpmyfaqto 4.1.4 or later - Upgrade
phpmyfaq/phpmyfaqto 4.1.4 or later
- Upgrade