Is WP Webhooks safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (3.5.0). As of 2026-11-04. 3 issues are on record for older versions; version 3.3.9 or newer fixes all of them that state a fix. Keep WP Webhooks on the latest version (3.5.0) and remove it if you do not use it.

Which versions of WP Webhooks are vulnerable?

Known issues on record (newest first): Arbitrary file upload (3.3.8 and older, fixed in 3.3.9); PHP object injection (3.3.8 and older, fixed in 3.3.9); Path traversal / file read (3.3.5 and older, fixed in 3.3.6). The full list with sources is on this page.

What is the latest version of WP Webhooks?

3.5.0, according to wordpress.org (last updated 2026-10-08). It has 20,000+ active installs.

What should I do if my WP Webhooks is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wp-webhooks). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · wp-webhooks · data as of 2026-11-04

Is WP Webhooks safe? Known vulnerabilities and latest version

Latest version: 3.5.0
Last updated: 2026-10-08
Active installs: 20,000+
Known issues on record: 3
Unpatched in latest: 0
Tested up to WP: 7.1.4

Automate everything & connect your website, plugins and services together with no-code automations. Browse 100+ integrations... — by Cozmoslabs

What to do

Update to the latest version (3.5.0). Anything older than 3.3.9 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get wp-webhooks --field=version shows what you run; wp plugin update wp-webhooks updates it.

Check your version

Known vulnerabilities

3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

critical 9.0 CVE-2025-66074 · published 2025-12-18

Arbitrary file upload in WP Webhooks (3.3.8 and older)

Affected: 3.3.8 and older
Fixed in: 3.3.9
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unrestricted Upload of File with Dangerous Type vulnerability in Cozmoslabs WP Webhooks wp-webhooks allows Path Traversal.This issue affects WP Webhooks: from n/a through <= 3.3.8.

NVD CVE-2025-66074 Patchstack advisory

high 7.2 CVE-2025-66073 · published 2025-11-21

PHP object injection in WP Webhooks (3.3.8 and older)

Affected: 3.3.8 and older
Fixed in: 3.3.9
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Deserialization of Untrusted Data vulnerability in Cozmoslabs WP Webhooks wp-webhooks allows Object Injection.This issue affects WP Webhooks: from n/a through <= 3.3.8.

NVD CVE-2025-66073 Patchstack advisory

critical 9.8 CVE-2025-8895 · published 2025-08-21

Path traversal / file read in WP Webhooks (3.3.5 and older)

Affected: 3.3.5 and older
Fixed in: 3.3.6 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2025-8895 Wordfence advisory Code change (fix)wordpress.org

Recent activity

2026-10-08 — latest release on wordpress.org (3.5.0).
2025-12-18 — Arbitrary file upload disclosed (CVE-2025-66074), fixed in 3.3.9.
2025-11-21 — PHP object injection disclosed (CVE-2025-66073), fixed in 3.3.9.
2025-08-21 — Path traversal / file read disclosed (CVE-2025-8895), fixed in 3.3.6.

Free. We check the CVE feeds every day and email you only when a new issue for WP Webhooks (wp-webhooks) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Arbitrary file upload (1) · PHP object injection (1) · Path traversal and file read (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/wp-webhooks (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/wp-webhooks"><img src="https://laskyr.com/plugins/wp-webhooks/badge.svg" alt="WP Webhooks vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is WP Webhooks safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.5.0)

What to do

Check your version

Known vulnerabilities

Arbitrary file upload in WP Webhooks (3.3.8 and older)

PHP object injection in WP Webhooks (3.3.8 and older)

Path traversal / file read in WP Webhooks (3.3.5 and older)

Recent activity

Get an email when WP Webhooks has a new vulnerability

Browse vulnerabilities

Where this data comes from