Ninja FormsWordPress extension · Ninjaforms
CVE-2017-18574
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 · uneditedThe ninja-forms plugin before 3.0.31 for WordPress has insufficient HTML escaping in the builder.
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 confidenceThe ninja-forms WordPress plugin before version 3.0.31 contains insufficient HTML escaping in its form builder component, allowing attackers to inject malicious HTML/JavaScript that executes in the browsers of users viewing affected forms.
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.0.31CVSS 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.0/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.
-
Verify Ninja Forms plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Ninja Forms' or check the /wp-content/plugins/ directory for the ninja-forms folderAffected if Ninja Forms plugin is not installed on the WordPress site
-
Check installed Ninja Forms versionIn WordPress admin, go to Plugins > Installed Plugins, find Ninja Forms, and note the version number displayedAffected if Version number displayed is lower than 3.0.31 (e.g., 3.0.30, 3.0.25, etc.)
-
Confirm form builder is in useCheck if any forms have been created in Ninja Forms by accessing Forms > Dashboard in WordPress admin; the vulnerability affects the form builder componentAffected if Forms exist or have been edited using the Ninja Forms form builder in versions below 3.0.31
-
Inspect rendered form outputView a published form on the site frontend and view the page source; check if HTML input fields contain unescaped special characters that could indicate injection vulnerabilityAffected if Form fields display raw HTML characters without proper escaping in versions below 3.0.31
The site is affected if Ninja Forms plugin version is below 3.0.31 AND forms created with the form builder are displayed on the site.
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.
From vendor data3.0.31
Update ninja-forms plugin to version 3.0.31 or later; test form functionality after update in a staging environment before production deployment.
Fix this in Ninja Forms
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18574 — 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-2017-18574 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