dbcve.org
Ninja Forms File UploadsWordPress extension · Ninjaforms

CVE-2022-0889

MEDIUM · 6.1 CVSS v3.1 Published 2022-03-23
Fix available
A fix is available. Upgrade to after 3.3.12 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 - File Uploads Extension WordPress plugin is vulnerable to reflected cross-site scripting due to missing sanitization of the files filename parameter found in the ~/includes/ajax/controllers/uploads.php file which can be used by unauthenticated attackers to add malicious web scripts to vulnerable WordPress sites, in versions up to and including 3.3.12.

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 File Uploads Extension WordPress plugin (versions up to 3.3.12) contains a reflected cross-site scripting (XSS) vulnerability due to insufficient sanitization of the filename parameter in ~/includes/ajax/controllers/uploads.php. Unauthenticated attackers can inject malicious JavaScript via the filename parameter that executes in victim browsers.

MitigationUpdate the Ninja Forms File Uploads Extension to version 3.3.13 or later, which includes proper input sanitization and output encoding of the filename parameter.

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 Forms File UploadsWordPress extension
Affected:<= 3.3.12

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.1/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 File Uploads plugin is installed
    Check your WordPress plugins directory for the Ninja Forms plugin or view it in the WordPress admin Plugins page. Look for 'Ninja Forms File Uploads' or 'File Uploads' extension.
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed version
    Open the main plugin file (typically in wp-content/plugins/ninja-forms-file-uploads/ or similar path) and check the Version header in the plugin comments, or check the readme.txt file.
    Affected if Version is 3.3.12 or lower (any version up to and including 3.3.12)
  3. Verify vulnerable file exists
    Check if the file includes/ajax/controllers/uploads.php exists within the plugin directory.
    Affected if The file exists at the expected path within the plugin folder
  4. Confirm file upload functionality is accessible
    Check if the WordPress ajax endpoint /wp-admin/admin-ajax.php is accessible and the plugin's upload action is registered. Test if the uploads functionality is enabled for forms.
    Affected if The plugin upload functionality is enabled and accessible to unauthenticated users

You are affected if the Ninja Forms File Uploads Extension plugin is installed with version 3.3.12 or lower and the file upload feature is active.

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 a release after 3.3.12
Interim mitigation

Update the Ninja Forms File Uploads Extension to version 3.3.13 or later, which includes proper input sanitization and output encoding of the filename parameter.

Recommended fix High confidence

Ninja Forms File Uploads version 3.3.13 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Ninja Forms File Uploads' plugin
  4. Check if the current version is 3.3.12 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/ninja-forms-uploads and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version is above 3.3.12

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

Fix this in Ninja Forms File Uploads Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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