CVE-2021-4436 is a critical (CVSS 9.8) unrestricted file upload flaw in the 3DPrint Lite plugin for WordPress, affecting versions before 1.9.1.5. Unauthenticated users can upload arbitrary files. Update to 1.9.1.5 or later, or remove the plugin if you do not use it.
What's affected
- 3DPrint Lite (3dprint-lite) for WordPress, all versions before 1.9.1.5, per the record and WPScan.
- Fixed in 1.9.1.5, per WPScan.
- The record notes that a .htaccess file in the upload location blocks direct access to the file on web servers such as Apache. That reduces the risk there, but the record does not say the same holds on other servers, and the missing authorization and file checks are still the defect.
- KEV status: false in the record.
How to check if you're exposed
List plugin versions from the WordPress admin, or with WP-CLI.
wp plugin list --fields=name,status,version
If 3dprint-lite appears at any version below 1.9.1.5, it is affected. Also inspect the plugin upload directory for files you do not recognise, especially executable types.
What to do now
- Update 3DPrint Lite to 1.9.1.5 or later, or delete it if the 3D printing quote feature is not in use.
- Check the plugin upload directories for unexpected files and remove anything you cannot account for.
- Confirm that your web server configuration prevents execution of scripts from upload directories, rather than relying on a plugin supplied .htaccess file alone.
- Review web server logs for requests to admin-ajax.php from unfamiliar addresses around the time the plugin was exposed.
- Keep a list of plugins that accept uploads, since they are the highest value targets.
Why it matters
The class is CWE-434, unrestricted upload of a file with a dangerous type. The record says the plugin handles the upload in an AJAX action without any authorization check and without validating the file. Two controls are missing at once: who may upload, and what may be uploaded.
The .htaccess detail is a good example of defense in depth working by luck rather than design. It may stop the stored file from being run on Apache, but a different server, a changed configuration or a later bug could remove that protection. Closing the real gap, by patching and by denying script execution in upload directories, is more dependable.
Quick check
Am I safe if I run Apache?
The record says the shipped .htaccess prevents access to the uploaded file on servers such as Apache, which lowers the risk. It does not remove the flaw, so update anyway.
What is the fixed version?
1.9.1.5, according to the record and the WPScan entry.
Sources
Last reviewed: 19 October 2026.