CVE-2026-46365

phpMyFAQ - Missing Authorization in Tag Deletion Endpoint

Published May 15, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability lies in the DELETE /admin/api/content/tags/{tagId} endpoint of phpMyFAQ prior to 4.1.2. It lacks proper authorization checks, allowing any authenticated user to request the deletion of a tag by supplying a valid session cookie. The action removes the tag permanently, causing loss of organized content in the FAQ module and potential confusion for end users. This flaw does not enable code execution or data exfiltration, but it delivers persistent data‑loss impact and undermines the integrity of the FAQ content.

Affected Systems

phpMyFAQ is distributed by the Thorsten team. All installations running phpMyFAQ before version 4.1.2 are susceptible because this version contains the unauthenticated deletion logic. Users of later releases are safe. The vulnerability is tied to the web application's administrative API.

Risk and Exploitability

Since the flaw appears only after the user has authenticated to the web application, any compromised or voluntarily logged‑in user can exploit it. No special network access or elevated privileges beyond standard authentication are required. The CVSS base score of 5.3 indicates a medium severity due to the potential for persistent data loss. The EPSS score is < 1% (approximately 0.0004), indicating a very low but non‑zero likelihood of exploitation, and the issue is not listed in CISA’s KEV catalogue, suggesting limited publicly known exploitation. In environments where many users have access, the risk of accidental or malicious tag deletion rises, warranting prompt attention.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.1.2 or later where the deletion endpoint includes proper authorization checks.
  • Restrict the DELETE /admin/api/content/tags/{tagId} endpoint to administrative roles only by enforcing role‑based access control in the application configuration.
  • Disable or remove the tag deletion API if tag management is not required, or monitor delete actions for suspicious activity.

Generated by OpenCVE AI on May 28, 2026 at 17:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-5h62-f8fg-4w7q phpMyFAQ: Missing Authorization on Tag Deletion Allows Any Authenticated User to Delete Tags
History
Type Values Removed Values Added
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Thorsten
Thorsten phpmyfaq
Vendors & Products Thorsten
Thorsten phpmyfaq
Type Values Removed Values Added
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.
Title phpMyFAQ - Missing Authorization in Tag Deletion Endpoint
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 8, 2026, 2:03 PM
Reserved
May 13, 2026, 7:40 PM
Status
Deferred
Published
May 15, 2026, 7:17 PM
Modified
Oct 26, 2026, 2:10 PM