CVE-2026-19793 json
WP Import Export Lite <= 3.9.32 - Unauthenticated Stored Code Execution via Placeholder Substitution in Imported Comment Content
published yesterday modified yesterday also EUVD-2026-131939
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
The WP Import Export Lite plugin for WordPress is vulnerable to Limited Code Injection in all versions up to, and including, 3.9.32 via the 'comment' parameter. This is due to a two-stage shortcode check that evaluates the raw mapping placeholder before data substitution, causing the neutralizer to be skipped when attacker-controlled comment content containing a malicious [wpie_function] shortcode is substituted at runtime. This makes it possible for unauthenticated attackers to inject arbitrary PHP callables on the server. Exploitation requires an Administrator to perform the standard Export With Settings For Import followed by a New Import migration workflow, which is a routine operational task; the attacker themselves requires no account or authentication, needing only the ability to submit a pending comment on any comments-open post.
Is CVE-2026-19793 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.79% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- vjinfotech WP Import Export Lite
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/46842ef6-9b28-44c5-a059-f696155829a6?source=cve
- plugins.trac.wordpress.org /browser/wp-import-export-lite/trunk/includes/classes/import/class-wpie-import-base.php#L285
- plugins.trac.wordpress.org /browser/wp-import-export-lite/trunk/includes/classes/import/class-wpie-import-base.php#L142
- plugins.trac.wordpress.org /browser/wp-import-export-lite/trunk/includes/classes/import/class-wpie-import-base.php#L182
- plugins.trac.wordpress.org /browser/wp-import-export-lite/trunk/includes/classes/import/class-wpie-import-base.php#L199
- plugins.trac.wordpress.org /browser/wp-import-export-lite/trunk/includes/classes/import/class-wpie-comment.php#L67
- plugins.trac.wordpress.org /browser/wp-import-export-lite/trunk/includes/classes/export/class-wpie-comment.php#L409
- plugins.trac.wordpress.org /browser/wp-import-export-lite/trunk/includes/classes/class-wpie-general.php#L586
- plugins.trac.wordpress.org /changeset/3685953/wp-import-export-lite/trunk/includes/classes/import/class-wpie-import-base.php
Sources
- CVE List CVE-2026-19793
- NVD CVE-2026-19793
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.