Ninja FormsWordPress extension · Ninjaforms
CVE-2020-36174
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.4.27.1 for WordPress allows CSRF via services integration.
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 confidenceThe Ninja Forms WordPress plugin before version 3.4.27.1 contains a Cross-Site Request Forgery (CSRF) vulnerability in its services integration feature. Attackers can trick authenticated users into unknowingly submitting malicious requests to the services integration endpoint due to missing or improper nonce validation.
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.4.27.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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Check if Ninja Forms plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Ninja Forms' in the list of active plugins.Affected if Ninja Forms plugin appears in the installed plugins list and is active.
-
Identify the installed Ninja Forms versionIn WordPress admin, go to Plugins > Installed Plugins, find Ninja Forms, and note the version number displayed below the plugin name. Alternatively, check the version in the plugin's main PHP file (ninja-forms.php) in wp-content/plugins/ninja-forms/.Affected if The version number is lower than 3.4.27.1 (for example, 3.4.27, 3.4.26, 3.4.25, etc.).
-
Determine if services integration feature is in useIn WordPress admin, navigate to Ninja Forms > Settings or look for any configured integrations with third-party services (such as email marketing platforms, CRM systems, or webhook connections). Check the plugin's settings pages for active service connections.Affected if Any third-party services or integrations are configured or enabled within the Ninja Forms plugin settings.
-
Verify if the site handles form submissions with state-changing operationsReview whether any Ninja Forms on the site process and store form submissions, send notification emails, or trigger external webhook requests when users submit forms.Affected if Forms are published and accepting submissions from users, particularly forms that trigger any automated actions or external communications.
A site is affected if Ninja Forms plugin version is below 3.4.27.1 AND the services integration feature is configured or forms are actively accepting submissions that could trigger external actions.
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.4.27.1
Update Ninja Forms plugin to version 3.4.27.1 or later. Additionally, ensure proper anti-CSRF nonce validation is implemented for all state-changing operations in the services integration functionality.
Fix this in Ninja Forms
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36174 — 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-2020-36174 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