Ninja FormsWordPress extension · Ninjaforms
CVE-2024-39628
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Saturday Drive Ninja Forms allows Cross Site Request Forgery.This issue affects Ninja Forms: from n/a through 3.8.6.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Ninja Forms WordPress plugin (versions up to 3.8.6) allows attackers to forge requests on behalf of authenticated users. The plugin lacks proper anti-CSRF token validation on form submissions and/or AJAX endpoints, enabling malicious actions to be performed without the user's consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ninja FormsWordPress extension
< 3.8.7CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Check installed Ninja Forms versionIn WordPress admin, go to Plugins > Installed Plugins > look for Ninja Forms and read the version number. Alternatively, check the plugin main file (typically wp-content/plugins/ninja-forms/ninja-forms.php) and look for the Version header comment.Affected if Version is lower than 3.8.7 (e.g., 3.8.6, 3.8.5, etc.)
-
Verify form submission handling lacks CSRF protectionInspect the plugin PHP files that handle form submissions (typically in the includes directory or Actions folder). Look for form processing code that does NOT call wp_verify_nonce() or check_admin_referer() before processing submitted data.Affected if Form submission handlers process data without validating a nonce token
-
Check AJAX endpoints for missing nonce verificationReview AJAX action handlers registered by the plugin (search for add_action with wp_ajax_ or wp_ajax_nopriv_). Verify if these handlers call wp_verify_nonce() or check_admin_referer() at the start of the callback function.Affected if AJAX endpoints process requests without verifying a CSRF token
-
Inspect frontend form output for nonce fieldsExamine the HTML output of any published Ninja Form. Check if the form includes a hidden nonce field (typically named _wpnonce or similar) or if forms are submitted without any token parameter.Affected if Forms render and submit without including a nonce token field
A user is affected if the installed Ninja Forms version is below 3.8.7 AND the plugin does not implement proper nonce verification on its form submissions or AJAX endpoints.
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.
dbcve · scoped3.8.7
Update Ninja Forms to the latest patched version when available. In the meantime, ensure WordPress nonces are implemented and verified on all form submissions and AJAX actions within the plugin.
Ninja Forms 3.8.7
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find Ninja Forms in the plugin list
- Check the current version number to confirm it is below 3.8.7
- Click 'Update Now' on the Ninja Forms plugin card if an update is available, or manually download version 3.8.7 from the WordPress plugin repository and upload it
- After updating, verify the new version is 3.8.7 or higher in Plugins > Installed Plugins
- Test form submission functionality to ensure the plugin is functioning correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ninja Forms
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39628 — 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-2024-39628 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