dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-13369

HIGH · 7.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

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 plugin for WordPress is vulnerable to Arbitrary File Read via the attach_files() function in versions up to, and including, 3.3.29. This is due to the get_files_for_attachment() function accepting a raw attacker-controlled 'files' array when the process() method returns early due to a client-supplied saveProgress flag, bypassing all upload validation, path normalization, and database record creation steps, and allowing an attacker-supplied file_path value to reach wp_mail() as an email attachment with only a file_exists() check. This makes it possible for unauthenticated attackers to read arbitrary files on the affected site's server.

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 plugin for WordPress (versions up to 3.3.29) contains an arbitrary file read vulnerability in its attach_files() function. When the process() method returns early due to a client-supplied saveProgress flag, the get_files_for_attachment() function accepts a raw attacker-controlled 'files' array, bypassing all upload validation, path normalization, and database record creation. An attacker-supplied file_path value reaches wp_mail() with only a file_exists() check, enabling unauthenticated attackers to read arbitrary server files.

MitigationUpdate the Ninja Forms File Uploads plugin to version 3.3.30 or later to patch this arbitrary file read vulnerability. Additionally, restrict file attachment email functionality or disable the plugin until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 File Uploads plugin is installed
    Check WordPress wp-content/plugins directory for ninja-forms-uploads folder, or view the Plugins page in WordPress admin to confirm the plugin is listed and activated
    Affected if The Ninja Forms File Uploads plugin is present and active in WordPress
  2. Confirm installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > find Ninja Forms File Uploads and read the version number from the plugin row. Alternatively, open the main plugin PHP file (usually ninja-forms-uploads.php) and check the 'Version' header comment
    Affected if Version is 3.3.29 or earlier (any version up to and including 3.3.29)
  3. Identify forms with file upload fields
    Navigate to Ninja Forms > Dashboard or Forms section in WordPress admin. Review each form to determine if any contain file upload fields (fields of type file upload or attachment)
    Affected if Any active form has a file upload field enabled and the form is in use
  4. Check file attachment email configuration
    In WordPress admin, go to Ninja Forms > Settings > File Uploads (or similar). Look for settings related to emailing file attachments or the 'attach_files' functionality. Check if email notifications are configured to include uploaded files
    Affected if Email notifications are configured to attach uploaded files to outgoing emails

You are affected if the Ninja Forms File Uploads plugin (versions up to 3.3.29) is installed and active with forms that have file upload fields configured, particularly if email notifications with file attachments are enabled

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Ninja Forms File Uploads plugin to version 3.3.30 or later to patch this arbitrary file read vulnerability. Additionally, restrict file attachment email functionality or disable the plugin until patched.

Recommended fix Moderate confidence

Ninja Forms File Uploads version 3.3.30 or latest available version

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Ninja Forms - File Uploads' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the new version is 3.3.30 or later
  6. 6. Test file upload functionality to ensure the plugin still works correctly

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

Have this fixed 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 help mitigating

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-2026-13369 — 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-2026-13369 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