Import Users From Csv With MetaWordPress extension · Codection
CVE-2019-15327
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 import-users-from-csv-with-meta plugin before 1.14.1.3 for WordPress has XSS via imported data.
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 · moderate confidenceThe import-users-from-csv-with-meta WordPress plugin before version 1.14.1.3 fails to properly sanitize or escape user data imported from CSV files before displaying it in the WordPress admin interface. This allows injected malicious JavaScript to execute in the browsers of administrators viewing imported user data, representing a stored XSS vulnerability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Import Users From Csv With MetaWordPress extension
< 1.14.1.3CVSS 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.0/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.
-
Check if the plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Import Users From Csv With Meta' or 'import-users-from-csv-with-meta' in the list.Affected if The plugin does not appear in the installed plugins list.
-
Determine the installed plugin versionIn the Plugins list, locate the 'Import Users From Csv With Meta' entry and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (typically /wp-content/plugins/import-users-from-csv-with-meta/import-users-from-csv-with-meta.php) and check the 'Version:' header comment.Affected if The version number shown is lower than 1.14.1.3.
-
Identify imported users in WordPressGo to Users > All Users in the WordPress admin dashboard. Review the user list to identify accounts that may have been created via CSV import. Check the user count and look for any users with suspicious display names, usernames, or metadata that could contain injected script tags.Affected if Users exist in the system, particularly those with unusual names or metadata that may have been imported from external CSV files.
-
Examine user metadata for malicious contentFor each suspected imported user, click to edit the user profile. Review all fields (especially custom meta fields) for any content containing script tags, javascript:, or HTML elements that were not intentionally added by administrators.Affected if Any user data fields contain unescaped HTML, script tags, or JavaScript event handlers.
The environment is affected if the plugin version is below 1.14.1.3 AND any users have been imported from CSV files AND an administrator views those user profiles in the admin interface, which would trigger the stored XSS.
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 data1.14.1.3
Update the plugin to version 1.14.1.3 or later. Until the update is applied, restrict CSV import permissions to highly trusted administrators only and review existing imported user data for suspicious content.
Fix this in Import Users From Csv With Meta
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15327 — 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-2019-15327 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