Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost malicious CSRF page
-
DeliveryLure logged-in admin to visit
-
ExploitBrowser auto-submits forged request
-
ExecutionExtension executes action with victim session
-
ImpactUnauthorized file upload or config change
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a victim who is currently authenticated to the target WordPress site (typically an administrator or other privileged user with access to the File Uploads Extension functionality) to be tricked into interacting with attacker-controlled content - the CVSS UI:R flag confirms mandatory user interaction. The attacker needs no account of their own (PR:N) and acts remotely over the network (AV:N/AC:L), but cannot succeed against a logged-out user, and the forged action is bounded by the privileges of the deceived session. The site must be running the Ninja Forms File Uploads Extension at version 3.3.26 or earlier; sites without this specific paid extension are not affected. The practical limiting factor is the need to both social-engineer a privileged, logged-in user and have the vulnerable extension installed. |
| Impact | The signals are partly conflicting and warrant scrutiny. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H = 9.6 Critical) is unusually aggressive for a CSRF issue: it claims full confidentiality, integrity, and availability impact plus a scope change, whereas most CSRF flaws deliver an integrity-only impact bounded by the privileges of the tricked user. UI:R is consistent with CSRF (the victim must be induced to trigger the request), and PR:N correctly reflects that the attacker themselves need no account. However, no EPSS score was provided, the vulnerability is not in CISA KEV (no confirmed active exploitation), and no public exploit was identified at time of analysis - so real-world exploitation pressure is currently low despite the critical rating. In practice, exploitability hinges on tricking a logged-in privileged user (e.g., an admin) into visiting a malicious page, which is a meaningful limiting factor. Treat this as a genuine high-priority patch item for sites running the extension, but note the C:H/I:H/A:H/S:C impact claim should be verified against the actual endpoint behavior, as it may overstate real impact. |
| Exploit ScenarioDerived | An attacker crafts a malicious web page or email containing a hidden auto-submitting form (or image tag) targeting the extension's state-changing endpoint on a victim WordPress site. When a logged-in administrator is lured into viewing that content, their browser silently submits the forged request with valid session cookies, causing the site to perform the attacker's action (e.g., an unauthorized file upload or setting change). No public exploit was identified at time of analysis, and success depends on the victim being authenticated and taking the bait (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 23, 2026
Cross-Site Request Forgery in the Ninja Forms File Uploads Extension for WordPress (versions 3.3.26 and earlier) lets a remote, unauthenticated attacker forge state-changing requests that are executed with a victim's session when the victim is lured into interacting with attacker-controlled content. Reported by Patchstack and rated CVSS 9.6 with a scope-changed, high-impact vector, the flaw carries no public exploit identified at time of analysis and is not listed in CISA KEV. Because it is a file-upload add-on, a successful forgery could result in unauthorized file uploads or configuration changes on the WordPress site.
RemediationAI
Upgrade the Ninja Forms File Uploads Extension to a release later than 3.3.26 once the vendor publishes a fixed build; a specific patched version number was not provided in the available data, so consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/ninja-forms-uploads/vulnerability/wordpress-ninja-forms-file-uploads-extension-plugin-3-3-26-cross-site-request-forgery-csrf-vulnerability) and the Saturday Drive account dashboard for the current release. Until a patch is applied, reduce exposure by having administrators avoid clicking untrusted links while logged into WordPress, ending admin sessions promptly (short cookie lifetime / log out when idle), and deploying a WordPress-aware WAF or Patchstack's virtual patching to block forged requests to the extension's endpoints - the trade-off is that aggressive request filtering can break legitimate form submissions and should be tuned. Where the file-upload functionality is not actively needed, temporarily deactivating the extension eliminates the attack surface at the cost of disabling file attachments on forms.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Ninja Forms File Uploads Extension, a commercial add-on to the widely used Ninja Forms WordPress form-builder plugin that adds file-attachment capabilities to forms. The root cause is CWE-352 (Cross-Site Request Forgery): one or more state-changing endpoints in the extension accept requests without validating an anti-CSRF nonce or equivalent origin token, so the WordPress-authenticated browser of a victim can be coerced into submitting a request the attacker composed. In WordPress, this is normally mitigated by wp_nonce fields and check_admin_referer()/wp_verify_nonce() validation; the absence or improper verification of that token is what makes the action forgeable. The CPE cpe:2.3:a:ninja_forms:ninja_forms_file_uploads_extension:*:*:*:*:*:*:*:* identifies the extension itself (all versions up to and including 3.3.26) rather than the Ninja Forms core plugin.
Know when Ninja Forms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CSRF needs no attacker auth (PR:N) but requires a logged-in victim to act (UI:R); impact is integrity-focused (unauthorized upload/change), with no inherent confidentiality or availability loss and no proven scope change, so I lower C/A and S versus the source.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Request Forgery (CSRF) in Ninja Forms File Uploads Extension <= 3.3.26 versions.
Executive ViewAI
A critical CSRF vulnerability in Ninja Forms File Uploads Extension (v3.3.26 and earlier) allows unauthenticated attackers to trick WordPress users into uploading malicious files or changing plugin settings, potentially leading to site compromise and data exfiltration. Any WordPress site using this plugin with user-submitted content is at risk of unauthorized file uploads and configuration tampering.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable plugin if non-essential; (2) Restrict upload permissions to administrator role; (3) Implement strict file-type whitelisting and execute-bit removal on all uploads; (4) Deploy WAF with CSRF token validation rules; (5) Enable detailed logging and alerting on file uploads and plugin configuration changes; (6) Apply Content Security Policy headers to prevent malicious script execution.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
More in Ninja Forms
View allThe Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
Stored cross-site scripting in the Ninja Forms WordPress plugin 3.15.3 lets an unauthenticated visitor plant a script pa
The AJAX action, wp_ajax_ninja_forms_sendwp_remote_install_handler, did not have a capability check on it, nor did it ha
The Ninja Forms plugin before 3.3.14.1 for WordPress allows CSV injection. Rated high severity (CVSS 8.6), this vulnerab
PHP Object Injection in the Ninja Forms WordPress plugin 3.15.3 allows unauthenticated attackers to plant serialized pay
The Ninja Forms Contact Form WordPress plugin before 3.6.13 unserialises the content of an imported file, which could le
The Ninja Forms Contact Form WordPress plugin before 3.6.4 does not escape keys of the fields POST parameter, which coul
The Ninja Forms WordPress plugin is vulnerable to sensitive information disclosure via the bulk_export_submissions funct
The Ninja Forms WordPress plugin before 3.8.11 does not escape an URL before outputting it back in an attribute, leading
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
The Ninja Forms Contact Form WordPress plugin before 3.6.22 does not properly escape user input before outputting it bac
In the Ninja Forms Contact Form WordPress plugin before 3.4.34, the wp_ajax_nf_oauth_connect AJAX action was vulnerable
EUVD-2026-48181
GHSA-vqq2-95gx-pw9q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB