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.
Published: 2026-05-15
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

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.4 indicates a medium severity due to the potential for persistent data loss. The EPSS data is not available 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.

Generated by OpenCVE AI on May 15, 2026 at 20:41 UTC.

Remediation

No vendor fix or workaround currently provided.

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 15, 2026 at 20:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 15 May 2026 22:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Fri, 15 May 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Thorsten
Thorsten phpmyfaq
Vendors & Products Thorsten
Thorsten phpmyfaq

Fri, 15 May 2026 19:00:00 +0000

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'}


Subscriptions

Thorsten Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-05-15T21:12:16.093Z

Reserved: 2026-05-13T19:40:27.809Z

Link: CVE-2026-46365

cve-icon Vulnrichment

Updated: 2026-05-15T21:12:07.993Z

cve-icon NVD

Status : Received

Published: 2026-05-15T19:17:03.860

Modified: 2026-05-15T22:16:56.530

Link: CVE-2026-46365

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-15T20:45:08Z

Weaknesses