dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14741

CRITICAL · 9.1 CVSS v3.1 Published 2026-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to missing authorization to unauthorized data modification and deletion due to a missing capability check on the 'delete_object' function in all versions up to, and including, 3.28.25. This makes it possible for unauthenticated attackers to delete arbitrary posts, pages, products, taxonomy terms, and user accounts.

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

The Frontend Admin plugin for WordPress contains a missing authorization vulnerability in the 'delete_object' function. The function lacks a capability check, allowing unauthenticated attackers to delete arbitrary posts, pages, products, taxonomy terms, and user accounts by making direct API requests.

MitigationUpdate to version 3.28.26 or later which implements proper capability checks. If immediate update is not possible, disable the plugin or restrict access to the affected endpoints at the web server level.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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 Frontend Admin plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Frontend Admin' or 'Front End Admin' in the list. Note whether it is Active or Inactive.
    Affected if The plugin is installed and marked as Active.
  2. Identify the installed version
    On the Plugins page, click on the plugin name or 'View Details' link for Frontend Admin. Note the version number displayed.
    Affected if The version number is lower than 3.26.27 (for example: 3.26.26, 3.25.x, or any earlier version).
  3. Verify the delete_object function is reachable
    Inspect the plugin files in wp-content/plugins/frontend-admin/ (or similar path). Look for files containing 'delete_object' function definition. Check if the function is hooked to an action accessible via wp-admin/admin-ajax.php or a public-facing endpoint without capability checks.
    Affected if The delete_object function exists and is hooked to an action accessible to unauthenticated users (no current_user_can() check present).
  4. Test external accessibility of affected endpoints
    Use a web proxy or curl to send a DELETE request to the site's admin-ajax.php endpoint with action parameter related to delete_object (e.g., ?action=fea_delete_object), without providing authentication cookies or credentials.
    Affected if The request does not return an authentication or capability error and the server processes the request.

A user is affected if the Frontend Admin plugin is active with a version lower than 3.26.27 AND the delete_object function is accessible to unauthenticated users without capability verification.

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

Update to version 3.28.26 or later which implements proper capability checks. If immediate update is not possible, disable the plugin or restrict access to the affected endpoints at the web server level.

Recommended fix Moderate confidence

Version 3.28.26 or later

  1. Update the Frontend Admin by DynamiApps plugin to the latest available version in the WordPress plugin repository
  2. Navigate to WordPress Admin > Plugins > Plugins List and check that the plugin shows version 3.28.26 or higher after update
  3. Verify the update completed successfully by confirming the plugin status is active

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
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14741 — 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-2025-14741 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