dbcve.org
Ninja FormsWordPress extension · Ninjaforms

CVE-2025-9083

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-18
Fix available
A fix is available. Upgrade to 3.11.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 WordPress plugin before 3.11.1 unserializes user input via form field, which could allow Unauthenticated users to perform PHP Object Injection when a suitable gadget is present on the blog.

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

The Ninja Forms WordPress plugin before version 3.11.1 insecurely deserializes user input submitted through form fields, enabling unauthenticated attackers to inject malicious PHP objects. Successful exploitation depends on the presence of a suitable 'gadget' chain (additional vulnerable code) within the WordPress environment that can be triggered via the injected object.

MitigationUpgrade Ninja Forms to version 3.11.1 or later immediately. Additionally, audit the WordPress environment for potentially dangerous deserialization gadget chains in other plugins or themes that could be chained with this 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.11.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Confirm Ninja Forms plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Ninja Forms' in the installed plugins list, or check the wp-content/plugins directory for the ninjaforms folder
    Affected if The plugin is present on the WordPress site
  2. Identify installed Ninja Forms version
    In WordPress admin, go to Plugins > Installed Plugins > Ninja Forms and read the version number displayed below the plugin name, or inspect the main plugin file header in wp-content/plugins/ninja-forms/ninja-forms.php for the 'Version' field
    Affected if Version number is less than 3.11.1 (e.g., 3.11.0, 3.10.x, etc.)
  3. Verify form submissions are accepted
    Check WordPress admin > Ninja Forms > Dashboard or Forms to confirm active forms exist and the plugin is configured to accept submissions, or review the site frontend for active contact/forms powered by Ninja Forms
    Affected if Ninja Forms is actively accepting user submissions through published forms
  4. Identify potential gadget chain sources
    Review installed plugins and themes for known PHP object injection gadget sources (common examples include popular plugins with unserialize calls or custom unserialize wrappers), check plugin list for unused or outdated plugins that could provide gadget chains
    Affected if Additional plugins or themes exist that could provide a gadget chain for object injection when combined with the vulnerable Ninja Forms deserialization

You are affected if Ninja Forms plugin version is below 3.11.1 AND the plugin is actively accepting form submissions on your site.

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.

dbcve · scoped
Upgrade available Upgrade to 3.11.1 or later
Fixed in 3.11.1
Interim mitigation

Upgrade Ninja Forms to version 3.11.1 or later immediately. Additionally, audit the WordPress environment for potentially dangerous deserialization gadget chains in other plugins or themes that could be chained with this vulnerability.

Recommended fix High confidence

3.11.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Ninja Forms in the plugin list
  4. If update available, click 'Update Now' to upgrade to version 3.11.1 or later
  5. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version from wordpress.org/plugins/ninja-forms/
  6. Verify the installed version is 3.11.1 or higher after updating

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
  • Testing3.0 h
  • Review / QA1.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-2025-9083 — 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-2025-9083 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