Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged authenticated account
-
DeliverySubmit crafted input via import/export user feature
-
ExploitPayload stored without neutralization
-
ExecutionAdmin views affected page (UI:R)
-
PersistScript executes in victim browser session
-
ImpactHijack session or perform privileged actions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account on the target WordPress site with enough privilege to reach the plugin's import/export user-and-customer functionality (CVSS PR:L), plus subsequent user interaction (UI:R) - a victim, typically an administrator or another user, must view the page where the payload is stored for the script to execute. The affected component is the 'Import and export users and customers' (import-users-from-csv-with-meta) plugin, versions up to and including 2.5.9. Limiting factors: it is not remote-unauthenticated (an account is needed), it does not self-trigger (it depends on a victim rendering the stored content), and the changed scope reflects execution in the victim's browser context rather than direct server compromise. The specific field or parameter carrying the unneutralized input is not described in the available sources. |
| Impact | This is a moderate-severity Stored Cross-Site Scripting flaw (CWE-79) in the Codection 'Import and export users and customers' WordPress plugin, scored CVSS 6.5. The provided CVSS vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) describes network-reachable, low-complexity exploitation but requires privileges (PR:L, i.e. an authenticated account) and victim user interaction (UI:R), with a changed scope (S:C) reflecting that injected script executes in another security context (the browser/session of whoever views the stored payload). The signals are mild rather than alarming: there is NO CISA KEV listing, NO EPSS score supplied, and NO verified working exploit - the single reference is a Patchstack database entry, not a proof-of-concept. The vulnerability was reported by Patchstack and carries a vuln.today priority Decision label of 'this_month', consistent with a real-but-not-emergency issue that should be remediated on a routine monthly patch cadence rather than treated as an active-exploitation fire drill. The combination of required authentication plus required user interaction meaningfully limits mass or opportunistic exploitation; this reads as a genuine but lower-tier priority, not a high-CVSS/low-real-risk false alarm nor a critical emergency. |
| Exploit ScenarioDerived | A low-privileged authenticated user stores a malicious script payload through the plugin's user/customer import or export handling, which fails to neutralize input during web page generation. When an administrator or other user later views the affected page in wp-admin, the stored script executes in their browser session, potentially performing actions as that higher-privileged victim. No verified public exploit code is available, so an attacker would need to craft the payload themselves. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Stored cross-site scripting in the Codection 'Import and export users and customers' WordPress plugin (import-users-from-csv-with-meta) allows an attacker holding a low-privileged authenticated account on a target site to persist script content that executes in another user's browser when that page is rendered. All versions through 2.5.9 are affected, per the Patchstack-reported CVE-2026-54862, which carries CVSS 3.1 base score 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L). The flaw is not remote-unauthenticated and does not self-trigger: it depends on a victim viewing the stored content, and no public exploit code, PoC reference, or CISA KEV entry is present in the available data, so no public exploit was identified at time of analysis.
RemediationAI
No vendor-released patch or fixed version is identified in the available data for CVE-2026-54862, so treat the current 2.5.9 and earlier releases as unfixed and monitor the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/import-users-from-csv-with-meta/vulnerability/wordpress-import-and-export-users-and-customers-plugin-2-5-9-cross-site-scripting-xss-vulnerability?_s_id=cve for a patched release, applying it as soon as it is published. Until a fix ships, the practical compensating control follows directly from the assessed prerequisites: the flaw requires an account with enough privilege to reach the plugin's import/export user-and-customer functionality, so restrict that capability to a small, trusted set of administrators and remove it from lower-privileged roles (for example via role/capability management), accepting the trade-off that delegated staff lose self-service CSV import/export. Because exploitation also requires a victim to render the stored content (UI:R), reducing the number of users who routinely open the plugin's administrative screens and reviewing recently imported records and user meta for injected markup limits exposure, with the trade-off of added manual review overhead. Disabling or removing the plugin entirely eliminates the attack surface at the cost of losing the import/export workflow; no parameter-level fix can be recommended here because the specific vulnerable field is not described in the available sources.
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 issue is CWE-79 (Improper Neutralization of Input During Web Page Generation), the classic stored/persistent XSS class, in a WordPress plugin whose purpose is importing and exporting user and customer records - typically CSV files with accompanying user meta. Because the plugin ingests externally supplied record data and later renders it back inside wp-admin pages, any field that is stored without output encoding becomes a script-injection sink that persists across requests. The assessed vector (PR:L, UI:R, S:C) makes clear this is not an unauthenticated server-side compromise: the attacker needs an account with sufficient privilege to reach the plugin's import/export functionality, and execution happens in the victim's browser session after the victim loads the affected page, which is why the scope is marked Changed rather than a direct server takeover. The specific vulnerable field, parameter, or rendering hook is not described in the available sources, and the CPE entry (cpe:2.3:a:codection:import_and_export_users_and_customers) is unversioned apart from the stated 'through 2.5.9' range, so the exact code path should be confirmed against the vendor or Patchstack advisory.
Know when Import And Export Users And Customers 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:L/UI:R/S:C/C:L/I:L/A:L
Stored XSS reachable over the network but requiring a logged-in account (PR:L) to inject and a victim's page view (UI:R); S:C because script runs in the victim's browser context, with limited C/I/A.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Codection Import and export users and customers import-users-from-csv-with-meta allows Stored XSS.This issue affects Import and export users and customers: from n/a through 2.5.9.
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 Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Privilege escalation in the "Import and export users and customers" WordPress plugin before 2.4.2 lets a user who holds
The Import and export users and customers WordPress plugin before 1.20.5 does not properly escape data when exporting it
Import and export users and customers WordPress Plugin through 1.15.5.11 allows CSV injection via a customer's profile.
Privilege escalation in the Import Export Users WordPress plugin before 2.5.2 allows authenticated users with the create
Privilege escalation in the Import and export users and customers WordPress plugin (versions 2.4.16 through before 2.5.2
Path traversal in the 'Import and export users and customers' WordPress plugin (versions before 2.4.3) enables high-priv
Privilege escalation in the WordPress plugin Import and Export Users and Customers (versions up to and including 2.4.17)
The Import and export users and customers WordPress plugin before 1.19.2.1 does not sanitise and escaped imported CSV da
Server-side request forgery in the WordPress plugin Import and Export Users and Customers (versions before 2.4.5) causes
The Import and export users and customers plugin for WordPress contains a privilege escalation vulnerability that allows
Privilege escalation in the WordPress plugin Import and Export Users and Customers (Javier Carazo) at versions up to and
Privilege escalation in the WordPress plugin Import and Export Users and Customers (versions through 2.5.5) allows an au
EUVD-2026-112822
GHSA-98p9-pqh4-fph5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB