dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-8895

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 WP Webhooks plugin for WordPress is vulnerable to arbitrary file copy due to missing validation of user-supplied input in all versions up to, and including, 3.3.5. This makes it possible for unauthenticated attackers to copy arbitrary files on the affected site's server to arbitrary locations. This can be used to copy the contents of wp-config.php into a text file which can then be accessed in a browser to reveal database credentials.

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 Webhooks plugin for WordPress versions up to 3.3.5 contains an arbitrary file copy vulnerability due to missing validation of user-supplied input. Unauthenticated attackers can copy any file from the server to any location, including copying wp-config.php to a web-accessible directory to exfiltrate database credentials.

MitigationUpdate WP Webhooks to version 3.3.6 or later immediately. If an update is unavailable, disable or remove the plugin. After updating, verify the wp-config.php file has not been compromised and review server access logs for signs of exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Locate WP Webhooks plugin files
    In the WordPress installation, navigate to /wp-content/plugins/ and look for a folder named 'wp-webhooks' or similar. Check the main plugin file (usually wp-webhooks.php or index.php) for the version number declared in the plugin header comment.
    Affected if The plugin is present and the version header shows 3.3.5 or lower.
  2. Retrieve installed version via WordPress admin
    Log into the WordPress admin dashboard, go to Plugins > Installed Plugins, find WP Webhooks in the list, and note the version number displayed beneath the plugin name.
    Affected if The displayed version is 3.3.5 or any version below 3.3.6.
  3. Check plugin active status
    In Plugins > Installed Plugins, verify whether WP Webhooks shows as 'Active' under the plugin status column.
    Affected if The plugin is active and the version is 3.3.5 or lower.
  4. Inspect web-accessible directories for copied config files
    Search web-root directories (public_html, www, htdocs, or the site root) for any files named wp-config.php.backup, wp-config.php.bak, wp-config.txt, config.php, or similarly named files that resemble the original wp-config.php. Use file system search or check via FTP/SSH.
    Affected if A duplicate or backup of wp-config.php exists in a web-accessible location outside the standard WordPress directory structure.
  5. Review server access logs for file copy patterns
    Examine HTTP access logs (usually in /var/log/apache2/, /var/log/nginx/, or your hosting provider's log viewer) for POST requests to the WP Webhooks endpoint (commonly /wp-json/wp-webhooks/v1/ or similar webhook URLs) combined with parameters indicating file operations.
    Affected if Logs show unauthenticated POST requests to webhook endpoints followed by unexpected file creation in web-accessible paths.

A user is affected if the WP Webhooks plugin is installed with version 3.3.5 or lower and is active, or if unexpected copies of wp-config.php exist in web directories.

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 WP Webhooks to version 3.3.6 or later immediately. If an update is unavailable, disable or remove the plugin. After updating, verify the wp-config.php file has not been compromised and review server access logs for signs of exploitation.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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