dbcve.org
Ninja FormsWordPress extension · Ninjaforms

CVE-2018-7280

MEDIUM · 6.1 CVSS v3.0 Published 2018-02-21
Fix available
A fix is available. Upgrade to 3.2.14 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 plugin before 3.2.14 for WordPress has XSS.

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

Cross-Site Scripting (XSS) vulnerability in the Ninja Forms WordPress plugin affecting versions prior to 3.2.14. The medium severity CVSS score of 6.1 indicates network-exploitable XSS that could allow attackers to inject malicious scripts into forms viewed by administrators or users.

MitigationUpdate Ninja Forms plugin to version 3.2.14 or later to remediate the XSS vulnerability.

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
Affected:< 3.2.14

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ninja Forms plugin is installed
    Log into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'Ninjaforms Ninja Forms' in the list
    Affected if Plugin is not found in the installed plugins list - not applicable
  2. Check installed plugin version
    In the Plugins list, locate Ninja Forms and note the version number displayed under the plugin name. Alternatively, check wp-content/plugins/ninja-forms/readme.txt for the 'Stable tag' entry
    Affected if Version number displayed is less than 3.2.14 (e.g., 3.2.13, 3.2.12, etc.)
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the Ninja Forms plugin shows as 'Active'
    Affected if Plugin is active AND version is below 3.2.14 - vulnerable to XSS exploitation
  4. Check for exposed form endpoints
    Visit your site and navigate to any page containing a Ninja Form shortcode (typically [ninja_form id=X]) or form preview page
    Affected if Forms are publicly accessible and plugin version is below 3.2.14

User is affected if Ninja Forms plugin is installed, active, and the installed version is lower than 3.2.14, allowing malicious script injection through form inputs.

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.

From vendor data
Upgrade available Upgrade to 3.2.14 or later
Fixed in 3.2.14
Interim mitigation

Update Ninja Forms plugin to version 3.2.14 or later to remediate the XSS vulnerability.

Fix this in Ninja Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7280 — 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-2018-7280 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