Debloat · Security record
Is Debloat safe?
No known vulnerability affects the current version (1.4.0). 1 issue was found in earlier versions and fixed, the latest disclosed on Oct 16, 2026.
Checked 3 days ago against the WPVulnerability database, for version 1.4.0.
How it’s looked after
- Last release
- Oct 9, 2026 (4 weeks ago)
- Releases in the last year
- 3
- Tested up to
- WordPress 7.1.4
- Support resolved
- 1 of 2 threads in two months
- Active installs
- 30K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in Debloat
Newest first, with any that affect the current version at the top.
Fixed in 1.4.0 · CVE-2026-104769 · Oct 16, 2026 · Wordfence
Questions about Debloat’s security
Is Debloat safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Debloat updated: most attacks target sites that haven’t updated.
Does Debloat have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Debloat up to date.
Is Debloat still maintained?
Yes. Its last release was 4 weeks ago. Its authors resolved 1 of the 2 support threads opened in the last two months.
Is Debloat compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.