CVE-2026-2830
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 · uneditedThe 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 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 confidenceThe WP All Import WordPress plugin is vulnerable to reflected Cross-Site Scripting (XSS) via the 'filepath' parameter in versions up to 4.0.0. The vulnerability stems from insufficient input sanitization and inadequate output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript through maliciously crafted URLs that trick users into clicking them.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP All Import plugin is installedLocate the wp-all-import plugin directory in your WordPress installation (typically wp-content/plugins/wp-all-import) or check via WordPress admin under Plugins > Installed PluginsAffected if The plugin directory exists in wp-content/plugins/ or appears in the WordPress admin plugin list
-
Check the installed version numberOpen the main plugin file (wp-all-import.php) and locate the version constant, or check the readme.txt file for the 'Stable tag' entryAffected if The version is 4.0.0 or any version prior to 4.0.0 (the plugin version displayed is 4.0.0 or lower)
-
Confirm the plugin is activeIn WordPress admin, verify the plugin status shows as 'Active' under Plugins > Installed Plugins, or query the wp_options table for option_name = 'active_plugins' containing 'wp-all-import'Affected if The plugin is enabled and running on the WordPress site
-
Identify if the vulnerable filepath parameter is reachableTest access to the plugin's admin interface or public-facing endpoint that handles the 'filepath' parameter. Common paths include /wp-admin/admin-ajax.php or the plugin's direct access files. Attempt a request with a harmless test parameter to observe if the filepath parameter is processedAffected if The endpoint responds and processes the filepath parameter without proper sanitization, indicating the vulnerable code path is accessible
You are affected if WP All Import version 4.0.0 or lower is installed and active, and the filepath parameter is processed by the plugin's vulnerable code path.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the WP All Import plugin to a version newer than 4.0.0 (or the latest patched version available). If immediate updating is not possible, implement web application firewall (WAF) rules to block requests with malicious filepath parameters as a temporary mitigation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2830 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2830 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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