dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14047

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Registration, User Profile, Membership, Content Restriction, User Directory, and Frontend Post Submission – WP User Frontend plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'Frontend_Form_Ajax::submit_post' function in all versions up to, and including, 4.2.4. This makes it possible for unauthenticated attackers to delete attachment.

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 WP User Frontend plugin for WordPress is vulnerable to broken access control due to a missing capability check on the Frontend_Form_Ajax::submit_post function in versions up to 4.2.4. This allows unauthenticated attackers to delete arbitrary attachments via the AJAX endpoint, as the function does not verify user permissions before processing deletion requests.

MitigationUpdate the WP User Frontend plugin to version 4.2.5 or later which includes proper capability checks. Until updated, monitor for suspicious unauthenticated AJAX requests to the site.

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
Low
Availability
None

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

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 WP User Frontend plugin is installed
    Navigate to WordPress admin > Plugins and locate 'WP User Frontend' in the installed plugins list, or inspect the plugin directory at /wp-content/plugins/wp-user-frontend/ and check the main PHP file for the version header
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    Read the version number from the plugin header in the main plugin file (commonly wp-user-frontend.php or class-frontend-form-ajax.php in the /includes or /classes directory)
    Affected if The version is 4.2.4 or lower (versions up to and including 4.2.4 are vulnerable)
  3. Locate the submit_post AJAX function
    Search the plugin files for 'Frontend_Form_Ajax::submit_post' or look for the AJAX handler that processes attachment deletion requests, typically in includes/class-frontend-form-ajax.php or similar
    Affected if The function exists and lacks a capability check (such as current_user_can() or wp_verify_nonce()) before processing deletion
  4. Verify the AJAX endpoint is exposed
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php is accessible (it is by default) and confirm the plugin registers an action hook for attachment deletion
    Affected if The AJAX endpoint is accessible and the plugin registers the vulnerable action without authentication requirements

The environment is affected if WP User Frontend plugin version 4.2.4 or lower is installed and the attachment deletion AJAX functionality is accessible without authentication.

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 the WP User Frontend plugin to version 4.2.5 or later which includes proper capability checks. Until updated, monitor for suspicious unauthenticated AJAX requests to the site.

Recommended fix Moderate confidence

Version higher than 4.2.4 (latest available version)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP User Frontend' plugin
  4. Check the current version installed
  5. If version is 4.2.4 or lower, click 'Update now' to upgrade to the latest version
  6. Verify the update completes successfully

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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