dbcve.org
Ninja FormsWordPress extension · Ninjaforms

CVE-2024-26019

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-11
Fix available
A fix is available. Upgrade to 3.8.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Ninja Forms prior to 3.8.1 contains a cross-site scripting vulnerability in submit processing. If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who is accessing to the website using the product.

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

Ninja Forms plugin before version 3.8.1 has a stored cross-site scripting (XSS) vulnerability in its form submit processing. When users submit forms, unsanitized input is stored and later rendered without proper output encoding, allowing injection of malicious JavaScript that executes in other users' browsers.

MitigationUpdate Ninja Forms to version 3.8.1 or later. After updating, verify that all form submissions still process correctly and that the XSS vulnerability is no longer exploitable.

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.8.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Ninja Forms plugin is installed
    Check your WordPress plugins directory or log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Ninja Forms' in the list of active plugins.
    Affected if Ninja Forms plugin appears in the installed plugins list
  2. Check the installed version of Ninja Forms
    In the WordPress admin, go to Plugins > Installed Plugins and locate Ninja Forms. The version number is displayed below the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/ninja-forms/readme.txt or the main plugin file.
    Affected if The version number displayed is lower than 3.8.1 (for example, 3.8.0, 3.7.x, or earlier)
  3. Confirm form submissions are enabled
    Navigate to Ninja Forms > Dashboard in the WordPress admin. Review your active forms and verify that form submission functionality is not disabled or restricted.
    Affected if Active forms exist and are configured to accept user submissions (this is the default state)
  4. Inspect stored form submissions for suspicious content
    In the WordPress admin, go to Ninja Forms > Submissions. Review recent form submissions for any content containing HTML tags, script elements, or JavaScript event handlers (such as <script>, onclick, onerror, or javascript: URIs).
    Affected if Any form submissions contain unencoded HTML, script tags, or JavaScript code that would execute when viewed

You are affected if Ninja Forms version is below 3.8.1 AND you have forms that accept user submissions, particularly if malicious JavaScript code is already present in stored submissions.

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.8.1 or later
Fixed in 3.8.1
Interim mitigation

Update Ninja Forms to version 3.8.1 or later. After updating, verify that all form submissions still process correctly and that the XSS vulnerability is no longer exploitable.

Recommended fix High confidence

3.8.1

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find Ninja Forms in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.8.1
  5. 5. Alternatively, navigate to Dashboard > Updates and select Ninja Forms to update
  6. 6. After updating, verify the plugin version is 3.8.1 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ninja Forms Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

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