CVE-2022-1538 is a high severity arbitrary file upload flaw in the Theme Demo Import WordPress plugin, scored 7.2 by NVD. It does not validate the imported file, so an admin can upload PHP even when file editing is disabled. The fix is version 1.1.1, so update or remove the plugin.
What's affected
The record says Theme Demo Import before 1.1.1 does not validate the imported file, allowing high privilege users such as admins to upload arbitrary files, such as PHP, even when the FILE_MODS and FILE_EDIT settings disallow it. The vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.
WPScan's entry, published 2022-11-08, says the plugin is fixed in 1.1.1, which matches the record. WPScan lists the plugin slug as theme-demo-import and the title as Theme-Demo-Importer.
The two sources differ on classification. NVD gives a score of 7.2 High and the weakness CWE-434, unrestricted upload of dangerous file types. WPScan gives 6.6 Medium and classifies it as CWE-94, code injection. Both describe the same behaviour: an admin account can place executable code on the server.
Weakness class: CWE-434.
How to check if you're exposed
If you use WP-CLI, list the plugin and its version with:
wp plugin list --fields=name,status,version | grep -i demo
wp plugin get theme-demo-import --field=version
Without WP-CLI, open the Plugins page in the admin area and read the version under the plugin name. Anything before 1.1.1 is in range. Check inactive plugins too, since a deactivated plugin's files stay on disk.
What to do now
- List every WordPress site you run and check for the plugin.
- Update to 1.1.1 or later, or delete the plugin if you no longer import demo content.
- Review the list of administrator accounts and remove any you do not recognise.
- Look in the uploads folder for PHP files, which have no reason to be there.
- Keep file editing disabled in production, but do not treat that setting as protection against this class of bug.
Why it matters
The notable point is the bypass. Many hardened WordPress sites set a constant that disables the file editor and plugin installs, to stop an admin account from adding code. The record says this plugin lets an admin upload code through its own import form, so the setting does not help. The weakness is CWE-434.
An admin account is already powerful, so a bug that needs one gets a lower score. The risk is the step after a stolen or phished admin password: instead of being limited by the hardening, the attacker can place a web shell. That turns a content takeover into a server takeover.
Demo import plugins are typically installed once and forgotten. If you no longer need one, deleting it is the best fix.
This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.
Quick check
Does disabling file edits protect me?
The record says the flaw works even when FILE_MODS and FILE_EDIT disallow changes, so no.
Why do NVD and WPScan differ?
NVD scores 7.2 High as an upload weakness. WPScan scores 6.6 Medium as code injection. The fixed version, 1.1.1, is the same in both.
Sources
Last reviewed: 19 October 2026.