CVE-2026-49205: phpMyFAQ missing authorization in API write endpoints

CVE-2026-49205 · Severity: medium · CVSS 6.5 · Published 2026-06-18

phpMyFAQ is an open-source FAQ software. A security flaw in its programming interface (API) allows any user with a valid API key to perform administrative actions, such as creating or editing FAQ entries and categories, even if their account does not have permission to do so. This could lead to unauthorized content modification or data manipulation by low-privileged users.

Technologies: phpmyfaq/phpmyfaq (Packagist), thorsten/phpmyfaq (Packagist), Thorsten phpMyFAQ. Vendors: Packagist, Thorsten.

Quick answers

Is CVE-2026-49205 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-49205 being exploited in the wild.
How severe is CVE-2026-49205?
Medium severity, with a CVSS score of 6.5, published 18 June 2026.
Which products and versions are affected?
phpmyfaq/phpmyfaq (Packagist) < 4.1.4, ECOSYSTEM:introduced=0,fixed=4.1.4; thorsten/phpmyfaq (Packagist) < 4.1.4, ECOSYSTEM:introduced=0,fixed=4.1.4; Thorsten phpMyFAQ < 4.1.4.
Is there a fix for CVE-2026-49205?
Yes. phpmyfaq/phpmyfaq (Packagist): upgrade to 4.1.4 or later; thorsten/phpmyfaq (Packagist): upgrade to 4.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49205 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-49205?
Check whether you run phpmyfaq/phpmyfaq (Packagist), thorsten/phpmyfaq (Packagist) or Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • phpmyfaq/phpmyfaq (Packagist): upgrade to 4.1.4 or later
    composer require phpmyfaq/phpmyfaq:^4.1.4
  • thorsten/phpmyfaq (Packagist): upgrade to 4.1.4 or later
    composer require thorsten/phpmyfaq:^4.1.4

Technical details

A missing authorization vulnerability exists in phpMyFAQ's API controllers. While the application validates the API token via hasValidToken(), it fails to call userHasPermission() for specific write operations in CategoryController, FaqController, and QuestionController. This is an incomplete fix for a previous issue (CVE-2026-24421). An attacker with a valid API token can bypass role-based access control (RBAC) to create categories, create/update FAQ entries, and create questions. The vulnerability is addressed in version 4.1.4 by implementing the missing userHasPermission() checks using existing PermissionType enums.

Affected products

  • thorsten phpMyFAQ < 4.1.4

Identifiers

  • CVE-2026-49205
  • GHSA-8c6h-7g6x-m5x4

Timeline

  • 2026-05-25: disclosed: Initial disclosure and patch commit
  • 2026-06-18: advisory: NVD publication
  • 2026-06-23: advisory: GitHub Advisory reviewed and published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.