CVE-2026-2830

WP All Import <= 4.0.0 - Reflected Cross-Site Scripting via 'filepath'

Strategic Overview

Status
Patched in 4.0.1
Affected Version
<= 4.0.0
CVSS
6.1Medium
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2026-2830
View all WP All Import – Drag & Drop Import for CSV, XML, Excel & Google Sheets vulnerabilities

At a glance

CVE-2026-2830 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the WP All Import WordPress plugin, affecting versions <= 4.0.0. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.0.1; sites on affected versions should update now. Disclosed March 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).

Vulnerability Overview

The WP All Import – Drag & Drop Import for CSV, XML, Excel & Google Sheets plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘filepath’ parameter in all versions up to, and including, 4.0.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-94: Improper Control of Generation of Code ('Code Injection')

WP All Import <= 4.0.0 carries this weakness at filepath, and reaching it takes a caller who can reach the endpoint. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For WP All Import the fix is 4.0.1: builds <= 4.0.0 are affected, anything from 4.0.1 onward is not.

Remediation

Update to version 4.0.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP All Import: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP All Import 4.0.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C