UsersWP: arbitrary file deletion
UsersWP
Arbitrary file deletion in the UsersWP component. Threat level: High (CVSS 8.1).
Who is affected
This vulnerability affects: UsersWP. If you use this component on your site, check the version and update it as soon as possible.
How dangerous
Rating: High, CVSS 8.1 out of 10. It is worth acting before the flaw is exploited.
What this flaw is
The flaw allows deletion of files the attacker should not be able to touch. In WordPress, deleting the right file is sometimes used to bypass install-time protections.
It can lead to a site outage and, in the right conditions, to a takeover through a repeated, controlled reinstall.
Score breakdown (CVSS vector)
What the CVSS 8.1 rating means in practice:
- The attack can be carried out remotely, over the internet.
- Requires an ordinary, low-privileged account.
- Requires no action from the victim.
- At risk: integrity (data can be altered), site availability.
Weakness class: CWE-22.
How to fix: arbitrary file deletion
- Update the vulnerable component to the fixed version.
- Until then, restrict access to the affected endpoint or disable the component.
- Verify that no key files are missing and that the site has not been reinstalled or reset by an attacker.
- Keep an off-site backup so a deletion cannot take the site down permanently.
Prefer not to do this yourself? We will handle the update, check for signs of a break-in and secure the site. Write to us →
Frequently asked questions
Does this vulnerability affect my site?
It affects sites that use UsersWP. Check whether you have this component installed and which version, the flaw only applies to the vulnerable version range. You can verify it in under a minute with our free vulnerability scanner.
How do I check whether I have the vulnerable version?
In your admin panel (in WordPress: Plugins / Themes) check the installed version of UsersWP and compare it with the vendor advisory that names the fixed version. If it is lower, or you are not sure, run our scanner, which reads the versions visible in the site code.
How urgently should I react?
This is a Wysoka-severity flaw, so treat it as urgent, high-impact vulnerabilities are often exploited automatically within hours of disclosure. Update as soon as possible.
What if a patch is not available yet?
Until a fix ships, reduce the exposure: temporarily disable the vulnerable component, restrict access to the affected functionality, or add a WAF rule blocking the vulnerable request. Keep a current off-site backup and watch for signs of a break-in.
Is updating alone enough?
If the site has not been attacked yet, updating to the patched version closes the hole. If there are already signs of compromise (unknown files, new admin accounts, redirects), the update does not undo the break-in, you also need to clean the site and rotate passwords and the WordPress salts.
Does this flaw affect your site?
We will run a free audit: we check versions, plugins, and configuration, and tell you plainly whether you are safe.
Request a free audit →