CVE-2026-46365
Description
phpMyFAQ before 4.1.2 contains a missing authorization vulnerability in the DELETE /admin/api/content/tags/{tagId} endpoint that allows any authenticated user to delete tags. Any logged-in user, including regular frontend users, can delete arbitrary tags by sending a DELETE request with a valid session cookie, resulting in permanent data loss and disruption of FAQ organization.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
phpMyFAQ before 4.1.2 allows any authenticated user to delete arbitrary tags via the DELETE /admin/api/content/tags/{tagId} endpoint due to missing permission checks.
Vulnerability
The TagController::delete() endpoint in phpMyFAQ (before version 4.1.2) at DELETE /admin/api/content/tags/{tagId} only verifies that the user is logged in via userIsAuthenticated() but does not enforce any specific permission check [1]. This contrasts with the update() and search() methods in the same controller, which properly require the FAQ_EDIT` permission [1]. The missing authorization allows any authenticated user—including regular frontend users—to delete tags by sending a DELETE request with a valid session cookie [1][2].
Exploitation
An attacker only needs a valid session cookie from any authenticated phpMyFAQ account, including a standard frontend user account. No special privileges or administrative access are required [1]. The attacker can enumerate or guess tag IDs and send a DELETE request to the vulnerable endpoint, causing permanent deletion of the specified tag [1][2].
Impact
Successful exploitation results in permanent data loss of tags and disruption of FAQ organization, as tags are used to categorize and retrieve FAQ entries [1][2]. The vulnerability has a CVSS v3 score of 5.4 (Medium) and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog [2].
Mitigation
The vulnerability is fixed in phpMyFAQ version 4.1.2 [1][2]. Users should upgrade immediately. No workaround is available for earlier versions.
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
2News mentions
0No linked articles in our index yet.