dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-46365

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

phpMyFAQ before 4.1.2 has a missing authorization vulnerability in the DELETE /admin/api/content/tags/{tagId} endpoint. The endpoint does not verify that the authenticated user has administrative privileges, allowing any logged-in user (including frontend users) to delete arbitrary tags by sending a DELETE request with a valid session cookie.

MitigationImplement proper role-based access control (RBAC) to verify that only authenticated users with admin privileges can access the DELETE tag endpoint. Add explicit authorization checks before executing tag deletion operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm phpMyFAQ installation and version
    Locate the phpMyFAQ installation directory and check the version.php file, or log into the admin dashboard and view the system information page. Look for a VERSION or version constant defining the installed version.
    Affected if Installed phpMyFAQ version is below 4.1.2
  2. Verify the admin API endpoint exists
    Check if the file handling the DELETE /admin/api/content/tags/{tagId} endpoint exists in the phpMyFAQ installation, typically under /admin/api/content/tags.php or similar routing configuration.
    Affected if The vulnerable endpoint file exists in the installation
  3. Test endpoint access with a non-admin user session
    Create a frontend (non-admin) user account, authenticate with that account to obtain a valid session cookie, then send a DELETE request to /admin/api/content/tags/1 (or any tagId) using that session. Observe if the request succeeds without returning an authorization error.
    Affected if A logged-in frontend user can successfully delete tags via the admin API endpoint
  4. Review session and authentication configuration
    Examine the phpMyFAQ configuration file (config/database.php or similar) and the authentication implementation in the source code to determine how user roles are validated for API requests.
    Affected if The authentication mechanism does not enforce admin role checks on the DELETE tag endpoint

You are affected if phpMyFAQ version is below 4.1.2 and the DELETE /admin/api/content/tags/{tagId} endpoint allows tag deletion by any authenticated user regardless of their privilege level.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper role-based access control (RBAC) to verify that only authenticated users with admin privileges can access the DELETE tag endpoint. Add explicit authorization checks before executing tag deletion operations.

Recommended fix Moderate confidence

phpMyFAQ 4.1.2 or later

  1. 1. Backup your current phpMyFAQ installation and database before performing any upgrade.
  2. 2. Download phpMyFAQ version 4.1.2 or later from the official phpMyFAQ website (phpmyfaq.de).
  3. 3. Extract the new version files and replace the existing installation, preserving your configuration and customizations.
  4. 4. Verify the admin/api/content/tags endpoint now properly enforces authorization checks.
  5. 5. Test that only users with admin privileges can delete tags through the API.
  6. 6. Confirm your FAQ organization and tags are intact after the upgrade.
Caveat Minor version upgrades typically don't introduce breaking changes, but review the changelog for any configuration or feature adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46365 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data