CVE-2025-66074
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 · uneditedUnrestricted 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.
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 confidenceThe WP Webhooks plugin versions up to 3.3.8 contain a path traversal vulnerability allowing attackers to upload files to arbitrary server locations by manipulating file path sequences in upload requests. Combined with unrestricted file type handling, this enables remote code execution by placing malicious scripts in web-accessible directories.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WP Webhooks plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-webhooks' or 'wp-webhooks-pro', or query the wp_options table for the active_plugins entry.Affected if The plugin folder exists in the WordPress installation.
-
Identify the installed versionOpen the main plugin file (e.g., wp-webhooks/wp-webhooks.php) and locate the Version header in the plugin comment block, or check the plugins admin page in WordPress dashboard.Affected if The version listed is 3.3.8 or any version below 3.3.8.
-
Verify the upload endpoint is accessibleCheck if the plugin's webhook receiving endpoint is exposed. Common paths include /wp-json/wp-webhooks/v1/ or similar REST API routes. Inspect the plugin's publicly accessible AJAX handlers or REST API routes.Affected if The upload/receiver endpoint responds without requiring authentication or with only basic authentication.
-
Check for unauthenticated access settingsReview the plugin settings under WP Webhooks > Settings > Receivers (or similar) to see if any receiver triggers are configured to accept unauthenticated requests.Affected if Any receiver is enabled that accepts unauthenticated or low-privilege webhook submissions.
If WP Webhooks version 3.3.8 or below is installed and the webhook receiver endpoint is accessible (especially to unauthenticated users), the environment is likely affected by this unrestricted file upload with path traversal vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade WP Webhooks to version 3.3.9 or later to obtain the security patch; additionally, restrict access to webhook endpoints via firewall rules or authentication until the update can be applied.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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