Ninja FormsWordPress extension · Ninjaforms
CVE-2024-29220
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 · uneditedNinja Forms prior to 3.8.1 contains a cross-site scripting vulnerability in custom fields for labels. If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who is accessing to the website using the product.
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 confidenceNinja Forms before 3.8.1 has a stored cross-site scripting vulnerability in custom field labels. Attackers with form editing access can inject malicious JavaScript into label fields, which executes when other users view or edit forms containing those fields.
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.1CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Ninja Forms versionNavigate to the WordPress admin dashboard, go to Plugins > Installed Plugins, locate Ninja Forms, and note the version number displayed. Alternatively, check the plugin header in the main plugin file (ninja-forms.php) or the version defined in the plugin's main PHP file.Affected if The installed version is lower than 3.8.1 (e.g., 3.8.0, 3.7.x, or earlier)
-
Confirm form editing access existsReview WordPress user roles and Ninja Forms-specific role capabilities to determine if any non-administrator users have permission to create or edit forms. Check under Ninja Forms > Settings > Role Settings or similar access control settings.Affected if Any user role other than administrator has form editing or form builder access
-
Locate custom field labels in existing formsAccess each form in the WordPress admin under Ninja Forms > Dashboard. Open each form in the form builder and review all field labels, particularly custom fields, merge tags, and label text settings for each field type.Affected if Forms contain custom field labels that can be edited
-
Inspect field labels for suspicious contentManually examine the label text of each field in the form builder. Look for unexpected HTML tags, script elements, event handlers (onclick, onload, onerror), javascript: URIs, or encoded characters that may indicate injected code.Affected if Any field label contains HTML script tags, javascript: protocols, or typical XSS payloads such as <script>, <img onerror=>, or <svg onload=>
You are affected if Ninja Forms version is below 3.8.1 AND any user with form editing access could have injected malicious JavaScript into custom field labels, which will execute when other users view or edit those forms.
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.1
Upgrade Ninja Forms to version 3.8.1 or later. Until patched, limit form editing to trusted administrators only and audit existing custom field labels for injected scripts.
Ninja Forms 3.8.1
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate Ninja Forms in the plugin list
- Click 'Update now' if an update is available, or manually update to version 3.8.1 or later
- Verify the update was successful by checking the plugin version
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
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29220 — 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-29220 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