dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-15470

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
The Eleganzo theme for WordPress is vulnerable to arbitrary directory deletion due to insufficient path validation in the akd_required_plugin_callback function in all versions up to, and including, 1.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary directories on the server, including the WordPress root directory.

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 Eleganzo WordPress theme up to version 1.2 contains a path traversal vulnerability in the akd_required_plugin_callback function that allows authenticated users with Subscriber-level permissions to delete arbitrary directories on the server due to insufficient path validation.

MitigationUpdate the Eleganzo theme to version 1.3 or later which includes proper path validation. Alternatively, remove the theme if not in use and disable user registration to prevent subscriber-level account creation.

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Eleganzo theme is installed
    Navigate to Appearance > Themes in WordPress admin, or run: wp theme list --status=active --format=csv
    Affected if Eleganzo theme appears in the installed themes list
  2. Identify Eleganzo theme version
    In WordPress admin, click on the Eleganzo theme details. Or check the style.css file in wp-content/themes/elegazo/ for the 'Version:' header. Or run: grep -i 'Version:' wp-content/themes/elegazo/style.css
    Affected if Version is 1.2 or lower (e.g., 1.2, 1.1, 1.0)
  3. Verify if user registration is enabled
    Go to Settings > General in WordPress admin and check 'Membership: Anyone can register'. Or run: grep -i 'users_can_register' wp-config.php
    Affected if 'Anyone can register' is checked/enabled, or 'users_can_register' is set to true
  4. Check for existing subscriber-level accounts
    Go to Users > All Users in WordPress admin and look for users with 'Subscriber' role. Or run: wp user list --role=subscriber --format=count
    Affected if Any subscriber accounts exist in the system

Environment is affected if Eleganzo theme version 1.2 or earlier is installed AND (user registration is enabled OR at least one subscriber account exists).

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Eleganzo theme to version 1.3 or later which includes proper path validation. Alternatively, remove the theme if not in use and disable user registration to prevent subscriber-level account creation.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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