dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-13411

MEDIUM · 6.4 CVSS v3.1 Published 2025-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 Zapier for WordPress plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.5.1 via the updated_user() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

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 Zapier for WordPress plugin for WordPress versions up to 1.5.1 contains a Server-Side Request Forgery (SSRF) vulnerability in the updated_user() function. This allows authenticated attackers with Subscriber-level access or higher to make the server perform web requests to arbitrary internal or external locations, potentially exposing internal services and sensitive data.

MitigationUpdate the Zapier for WordPress plugin to the latest version beyond 1.5.1, which should contain proper URL validation in the updated_user() function to prevent arbitrary request forwarding. If no patched version is available, consider disabling the plugin or implementing WAF rules to block suspicious outbound requests.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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. Verify Zapier for WordPress plugin is installed
    Navigate to WordPress Admin Dashboard > Plugins and look for 'Zapier for WordPress' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In the Plugins list, click on the plugin name or view details to see the installed version number, then compare it to 1.5.1
    Affected if The installed version is 1.5.1 or lower
  3. Confirm the updated_user() function is accessible
    Check if the WordPress Zapier integration is enabled - this function typically processes user data sent to Zapier webhooks; verify plugin settings allow user update triggers
    Affected if The plugin is active and user update webhooks are configured
  4. Identify user roles with access
    Go to WordPress Admin Dashboard > Users and review the existing user accounts to see if any have Subscriber-level or higher roles
    Affected if There are user accounts with Subscriber, Contributor, Author, Editor, or Administrator roles

You are affected if the Zapier for WordPress plugin is installed with version 1.5.1 or lower, the plugin functionality is active, and your site has at least one user with Subscriber-level access or higher.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Zapier for WordPress plugin to the latest version beyond 1.5.1, which should contain proper URL validation in the updated_user() function to prevent arbitrary request forwarding. If no patched version is available, consider disabling the plugin or implementing WAF rules to block suspicious outbound requests.

Recommended fix High confidence

Version 1.5.2

  1. Log in to the WordPress admin dashboard.
  2. Navigate to the 'Plugins' menu.
  3. Locate 'Zapier for WordPress' in the installed plugins list.
  4. Click 'Update Now' to upgrade the plugin to version 1.5.2 or later.

Generated from the published advisory — verify against the referenced sources before acting.

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-2024-13411 — 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-2024-13411 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