Ninja FormsWordPress extension · Ninjaforms
CVE-2024-37934
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Saturday Drive Ninja Forms allows Code Injection.This issue affects Ninja Forms: from n/a through 3.8.4.
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 confidenceA code injection vulnerability in the Ninja Forms WordPress plugin (versions through 3.8.4) allows attackers to inject malicious code, potentially leading to remote code execution. The improper control of code generation enables attackers to leverage the plugin's input handling to execute arbitrary commands on the server.
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.5CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Confirm Ninja Forms plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the ninja-forms folder, or view the installed plugins list in the WordPress admin dashboard under PluginsAffected if The ninja-forms directory exists in the plugins folder
-
Identify installed Ninja Forms versionIn WordPress admin, go to Plugins > Installed Plugins and find the Ninja Forms plugin version number. Alternatively, open wp-content/plugins/ninja-forms/readme.txt and check the Version field in the header commentAffected if Unable to determine the version or version is displayed
-
Compare version against vulnerable rangeCompare the installed version to the affected range: any version below 3.8.5 is vulnerable. Versions 3.8.5 and above are patchedAffected if Installed version is 3.8.4 or lower
-
Check plugin status and accessibilityVerify the Ninja Forms plugin is active by checking the WordPress admin Plugins page. An active plugin with the vulnerability exposes the attack surfaceAffected if Ninja Forms is active and version is below 3.8.5
A WordPress site is affected if the Ninja Forms plugin is installed, active, and the installed version is 3.8.4 or lower (below 3.8.5).
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.5
Upgrade Ninja Forms to the latest patched version immediately. Given the CVSS 9.8 critical rating and code injection nature, treat this as a critical security incident requiring urgent remediation.
Ninja Forms version 3.8.5
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate Ninja Forms in the plugin list
- If an update is available, click 'Update Now' to upgrade to version 3.8.5
- Alternatively, go to Dashboard > Updates and select Ninja Forms to update
- After updating, verify the plugin version shows 3.8.5
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ninja Forms
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37934 — 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-37934 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