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

CVE-2024-13940

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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 Ninja Forms Webhooks plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.0.7 via the form webhook functionality. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and 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 Ninja Forms Webhooks plugin for WordPress (versions up to 3.0.7) contains a Server-Side Request Forgery (SSRF) vulnerability in its form webhook functionality. Authenticated administrators can abuse this to make arbitrary HTTP requests from the server, potentially reaching internal services and exfiltrating sensitive information.

MitigationUpdate the Ninja Forms Webhooks plugin to version 3.0.8 or later to remediate this vulnerability. If the plugin is not actively used, consider removing it entirely.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Ninja Forms Webhooks plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ninja Forms Webhooks' in the list. Alternatively, check the plugins directory on the server for a folder named 'ninja-forms-webhooks' or similar.
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version number
    In WordPress admin, go to Plugins > Installed Plugins and locate the version number listed beneath the Ninja Forms Webhooks plugin name. Compare this to the affected range of versions up to 3.0.7.
    Affected if The installed version is 3.0.7 or any earlier version (e.g., 3.0.6, 3.0.5, etc.)
  3. Verify webhook functionality is accessible
    Check if the Webhooks module is enabled in Ninja Forms settings. Look for Webhook-related settings under Ninja Forms > Settings or within individual form configurations. Inspect if any webhook endpoints have been configured.
    Affected if Webhook functionality is enabled and administrators can configure webhook URLs
  4. Confirm administrator access exists
    Review user roles with administrative privileges. The vulnerability requires an authenticated administrator to trigger the SSRF. Check if any user accounts have administrator-level access to the WordPress site.
    Affected if Administrator accounts exist and can access the Ninja Forms dashboard

A user is affected if the Ninja Forms Webhooks plugin is installed with version 3.0.7 or earlier and the webhook feature is accessible to administrators on the site.

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 Ninja Forms Webhooks plugin to version 3.0.8 or later to remediate this vulnerability. If the plugin is not actively used, consider removing it entirely.

Recommended fix Moderate confidence

Ninja Forms Webhooks version 3.0.8 or later

  1. Log in to the WordPress admin dashboard with Administrator privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Ninja Forms Webhooks plugin
  4. If an update is available, click 'Update Now' to upgrade to version 3.0.8 or later
  5. Alternatively, download the latest version from the official Ninja Forms WordPress repository or the plugin developer's website
  6. Deactivate and delete the old version if automatic update doesn't work, then upload and activate the new version
  7. Verify the plugin is running version 3.0.8 or higher after updating
Caveat No specific breaking changes documented for this security update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.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-13940 — 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-13940 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