Optimize Database after Deleting Revisions · Security record
Is Optimize Database after Deleting Revisions safe?
No known vulnerability affects the current version (5.3.0). 4 issues were found in earlier versions and fixed, the latest disclosed on Oct 4, 2023.
Checked 4 days ago against the WPVulnerability database, for version 5.3.0.
How it’s looked after
- Last release
- May 21, 2026 (5 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 7.0.8
- Active installs
- 60K+
4 known vulnerabilities
- 1 medium
- 3 not rated
None affects the current version.
Every known vulnerability in Optimize Database after Deleting Revisions
Newest first, with any that affect the current version at the top.
Fixed in 5.1 · Oct 4, 2023 · Patchstack
Fixed in 5.1 · Oct 3, 2023 · Wordfence
Fixed in 5.1.1 · CVE-2023-25980 · Jul 26, 2023 · Wordfence
Fixed in 5.1 · WPScan
Questions about Optimize Database after Deleting Revisions’s security
Is Optimize Database after Deleting Revisions safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Optimize Database after Deleting Revisions updated: most attacks target sites that haven’t updated.
Does Optimize Database after Deleting Revisions have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep Optimize Database after Deleting Revisions up to date.
Is Optimize Database after Deleting Revisions still maintained?
Yes. Its last release was 5 months ago. No support threads were opened in the last two months.
Is Optimize Database after Deleting Revisions compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
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.