Strategic Overview
- Status
- Patched in 3.3.6
- Affected Plugin
- WP Webhooks – Automate repetitive tasks by creating powerful automation workflows directly within WordPress
- Affected Version
<= 3.3.5- CVSS
- 9.8Critical
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-8895
At a glance
CVE-2025-8895 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP Webhooks WordPress plugin, affecting versions <= 3.3.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.3.6; sites on affected versions should update now. Disclosed August 2025, reported by Phat RiO.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in WP Webhooks <= 3.3.5 takes no account at all. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For WP Webhooks the fix is 3.3.6: builds <= 3.3.5 are affected, anything from 3.3.6 onward is not.
Remediation
Update to version 3.3.6, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Webhooks 3.3.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Webhooks – Automate repetitive tasks by creating powerful automation workflows directly within WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C