dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-0818

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
Several WordPress plugins using elFinder versions 2.1.64 and prior are vulnerable to Directory Traversal in various versions. This makes it possible for unauthenticated attackers to delete arbitrary files. Successful exploitation of this vulnerability requires a site owner to explicitly make an instance of the file manager available to users.

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

This vulnerability affects WordPress plugins bundling elFinder file manager versions 2.1.64 and prior. The directory traversal flaw allows unauthenticated attackers to delete arbitrary files on the server by manipulating file paths in elFinder requests. The attack surface is limited to sites where administrators have explicitly enabled public access to the file manager instance.

MitigationUpdate elFinder to a version newer than 2.1.64 or update the affected WordPress plugins to their latest versions. If immediate patching is not possible, restrict access to the file manager to authenticated users only or disable the plugin until a patch is available.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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. Locate elFinder installation in WordPress
    Search the wp-content/plugins directory for elFinder files, typically found in js/elfinder or similar paths within plugin folders
    Affected if elFinder is present and bundled with any WordPress plugin
  2. Identify elFinder version
    Open the elFinder JavaScript file (usually elfinder.min.js or core.js) and locate the version string in the file header or source code comments
    Affected if Version is 2.1.64 or lower
  3. Check if public access is enabled
    Examine the elFinder connector configuration file (typically connector.php or similar) for connector options that allow unauthenticated access, such as 'public' or 'isoffline' flags set to false or open access patterns
    Affected if The file manager is configured to accept requests from unauthenticated users without authentication verification
  4. Test for the traversal vulnerability
    If public access is confirmed, send a crafted elFinder request attempting to delete a file outside the intended root directory (e.g., using ../ paths in a delete command)
    Affected if The server accepts and processes directory traversal delete requests without validation

A user is affected if elFinder version 2.1.64 or lower is installed AND the file manager is configured to allow unauthenticated/public access.

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 elFinder to a version newer than 2.1.64 or update the affected WordPress plugins to their latest versions. If immediate patching is not possible, restrict access to the file manager to authenticated users only or disable the plugin until a patch is available.

Recommended fix Moderate confidence

elFinder version 2.1.65 or later (or the latest available release)

  1. Identify all WordPress plugins on the site that include elFinder file manager functionality
  2. Check the elFinder version bundled within each plugin (typically found in plugin's lib or vendor directories)
  3. Upgrade each affected plugin to its latest version, which should include elFinder version higher than 2.1.64
  4. Alternatively, if the plugin maintains elFinder as a separate component, update elFinder to the latest available release
  5. Verify the update was successful by confirming the elFinder version in the plugin
  6. Ensure the file manager is not exposed to unauthenticated users if full isolation is not possible

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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