dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-3055

HIGH · 8.1 CVSS v3.1 Published 2025-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
The WP User Frontend Pro plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_avatar_ajax() function in all versions up to, and including, 4.1.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 Pro WordPress plugin has an arbitrary file deletion vulnerability in the delete_avatar_ajax() function. Due to insufficient file path validation, authenticated users with Subscriber-level access or higher can manipulate file paths to delete arbitrary files on the server, including critical files like wp-config.php which can lead to remote code execution.

MitigationUpdate to the patched version of WP User Frontend Pro (greater than 4.1.3) or implement strict file path validation/sanitization in the delete_avatar_ajax() function to prevent path traversal attacks.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 WP User Frontend Pro is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP User Frontend Pro' in the list. Alternatively, check the plugins directory at wp-content/plugins/ for a folder starting with 'wp-user-frontend-pro' or similar.
    Affected if The plugin is not installed or has been removed entirely.
  2. Identify the installed plugin version
    In the WordPress admin Plugins list, locate WP User Frontend Pro and view the version number displayed below the plugin name. Or inspect the main plugin file header in wp-content/plugins/[plugin-folder]/wpuf-pro.php to read the 'Version' comment.
    Affected if The version is 4.1.3 or lower (the vulnerability exists in versions up to and including 4.1.3).
  3. Verify the vulnerable delete_avatar_ajax function exists
    Access the WordPress site files via FTP or file manager. Locate the WP User Frontend Pro plugin folder and search for the function named 'delete_avatar_ajax' within the PHP files. Confirm it exists and contains file deletion logic without proper path validation.
    Affected if The function exists in the plugin code, indicating the vulnerable code path is present.
  4. Confirm the ajax endpoint is accessible
    Check if the WordPress REST API or admin-ajax.php exposes the delete_avatar_ajax action. This can be tested by making a request to yoursite.com/wp-admin/admin-ajax.php?action=delete_avatar_ajax (or via REST API endpoint).
    Affected if The endpoint responds and accepts requests, making the vulnerability reachable.
  5. Check for low-privilege user accounts
    In WordPress admin, go to Users > All Users. Review the list of users and their assigned roles. Specifically identify any users with the Subscriber role or higher privilege level.
    Affected if At least one user account with Subscriber-level access or higher exists on the site.

You are affected if WP User Frontend Pro is installed with version 4.1.3 or lower, the delete_avatar_ajax function is present, and any subscriber-level user account exists on the site.

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 the patched version of WP User Frontend Pro (greater than 4.1.3) or implement strict file path validation/sanitization in the delete_avatar_ajax() function to prevent path traversal attacks.

Recommended fix Moderate confidence

WP User Frontend Pro version higher than 4.1.3 (check WordPress plugin repository or vendor for exact fixed release)

  1. Check your currently installed WP User Frontend Pro plugin version in WordPress admin under Plugins
  2. If running version 4.1.3 or lower, update to the latest available version of WP User Frontend Pro
  3. After updating, verify the delete_avatar_ajax() function behavior to confirm the path traversal is no longer exploitable
  4. Consider implementing additional server-side access controls as a defense-in-depth measure
  5. Review user role permissions to ensure subscribers only have necessary capabilities

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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