Ninja FormsWordPress extension · Ninjaforms
CVE-2024-25572
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 · uneditedCross-site request forgery (CSRF) vulnerability exists in Ninja Forms prior to 3.4.31. If a website administrator views a malicious page while logging in, unintended operations may be performed.
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 confidenceCross-site request forgery (CSRF) vulnerability in Ninja Forms plugin for WordPress versions prior to 3.4.31 allows remote attackers to execute unintended administrative actions by tricking a logged-in administrator into visiting a malicious page, leveraging the trust relationship between the authenticated user and the vulnerable application.
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.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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate Ninja Forms plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Ninja Forms and read the Version field. Alternatively, use WP-CLI: wp plugin list --name=ninja-forms --format=tableAffected if The version listed is lower than 3.4.31 (e.g., 3.4.30, 3.4.28, etc.)
-
Verify plugin is activeConfirm Ninja Forms shows as Active in the Plugins page or via: wp plugin list --name=ninja-forms --status=active --format=tableAffected if Plugin is active and version is below 3.4.31 - this creates the attack surface for CSRF exploitation
-
Identify administrative usersReview WordPress users with Administrator role at Users > All Users. The CSRF attack requires a logged-in administrator to inadvertently trigger the malicious request.Affected if There are logged-in administrator sessions that could be targeted by the CSRF attack vector
If Ninja Forms version is below 3.4.31 and the plugin is active on the site, the environment is vulnerable to CVE-2024-25572 CSRF attacks targeting administrators.
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.4.31
Upgrade Ninja Forms to version 3.4.31 or later to implement anti-CSRF tokens or same-site cookie protections. Ensure administrators are educated not to click untrusted links while authenticated.
Ninja Forms 3.4.31
- Backup your WordPress site before making any changes
- Navigate to your WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate Ninja Forms in the plugin list
- Update Ninja Forms to version 3.4.31 or later
- Verify the update was successful by checking the installed 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
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25572 — 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-25572 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