dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-30567

HIGH · 7.5 CVSS v3.1 Published 2025-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WP01 WP01 wp01 allows Path Traversal.This issue affects WP01: from n/a through <= 2.6.2.

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 · moderate confidence

Path Traversal vulnerability in WP01 WordPress plugin allows attackers to access files outside the web root directory through manipulation of file path parameters, potentially exposing sensitive system files or configuration data.

MitigationUpgrade WP01 to the latest version which includes proper path sanitization and input validation to prevent directory 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 WP01 plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or check /wp-content/plugins/ directory for wp01 folder
    Affected if WP01 plugin is present in the WordPress installation
  2. Identify installed WP01 version
    Check the plugin header in wp-content/plugins/wp01/wp01.php for 'Version:' field, or view in WordPress plugin admin page
    Affected if Version cannot be confirmed as the latest patched version (version comparison needed)
  3. Verify web server access logs for path traversal attempts
    Review Apache/nginx access logs for requests containing '../' patterns targeting WP01 plugin endpoints, e.g., grep -r "../" /var/log/apache2/ or /var/log/nginx/
    Affected if Logs show directory traversal patterns like '..' in file path parameters routed to WP01 plugin
  4. Check for unauthorized file access indicators
    Inspect web server error/access logs for repeated attempts to access paths outside web root (e.g., /etc/passwd, wp-config.php)
    Affected if Suspicious traversal patterns are found in logs targeting WP01 endpoints

You are affected if the WP01 plugin is installed and its version is older than the patched release, or if web server logs show path traversal attempts targeting WP01 plugin endpoints.

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

Upgrade WP01 to the latest version which includes proper path sanitization and input validation to prevent directory traversal attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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