CVE-2022-3899 is a high severity cross-site request forgery flaw in the 3dprint WordPress plugin before 3.5.6.9, scored 8.1 by NVD. Its bundled file manager can be tricked into deleting files and directories through a logged in admin. Update to 3.5.6.9 or later.
What's affected
The record says the 3dprint plugin before 3.5.6.9 does not protect against CSRF attacks in the modified version of Tiny File Manager that it includes. An attacker can craft a request that deletes any number of files or directories on the server by tricking a logged in admin into submitting a form. The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H.
WPScan's entry lists the plugin as 3dprint and the fix as 3.5.6.9, matching the record. WPScan scores it 8.2 High while NVD scores 8.1 High, a rounding level difference, so the sources agree that it is high.
WPScan adds that file paths are relative to the plugin's upload folder and that directories are deleted recursively, so a single request can remove a lot.
Weakness class: CWE-352.
How to check if you're exposed
With WP-CLI:
wp plugin get 3dprint --field=version
Or read the version on the Plugins page of the admin area. Anything before 3.5.6.9 is in range. Check deactivated plugins too, because their files remain on disk and some flaws can be reached without the plugin being active.
What to do now
- Find the sites running 3dprint.
- Update to 3.5.6.9 or later.
- Make sure you have a recent backup of both files and the database, in case something was removed.
- Ask administrators to log out of the dashboard when they browse other sites.
- Remove the plugin if you no longer sell print services through it.
Why it matters
Cross-site request forgery works because browsers attach cookies automatically. If a logged in admin visits a page that submits a form to your site, the request arrives with the admin's session, and the server cannot tell it was not intended. The defence is a secret token tied to the session that every state changing request must carry. The record says the bundled file manager had none. The weakness is CWE-352.
The bundled component is the interesting part. The plugin carries a modified copy of a third party file manager, and the modification left out the protection. Embedded copies of open source tools need their own review, because upstream fixes do not reach them automatically.
The effect is deleting files, which can include configuration files that keep the site running. That is an availability and integrity problem without any code execution, and a restore from backup is the recovery path.
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 the attacker need a login?
Not on your site, but a logged in admin must be tricked into submitting a form, which is why the vector includes user interaction.
What can be deleted?
The record says any number of files or directories on the server. WPScan adds that paths are relative to the plugin's upload folder and directories are removed recursively.
Sources
Last reviewed: 19 October 2026.