Safety Exit · Security record
Is Safety Exit safe?
No known vulnerability affects the current version (1.8.1). 2 issues were found in earlier versions and fixed, the latest disclosed on Sep 22, 2025.
Checked 2 days ago against the WPVulnerability database, for version 1.8.1.
How it’s looked after
- Last release
- Sep 30, 2025 (1 year ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.8.12 (current: 7.1)
- Active installs
- 1K+
2 known vulnerabilities
- 2 medium
None affects the current version.
Disclosed each year
- 20241
- 20251
Every known vulnerability in Safety Exit
Newest first, with any that affect the current version at the top.
Fixed in 1.8.1 · CVE-2025-57980 · Sep 22, 2025 · Wordfence
Fixed in 1.7.1 · CVE-2024-35640 · May 30, 2024 · Wordfence
Questions about Safety Exit’s security
Is Safety Exit safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Safety Exit updated: most attacks target sites that haven’t updated.
Does Safety Exit have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep Safety Exit up to date.
Is Safety Exit still maintained?
Its last release was 1 year ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is Safety Exit compatible with the latest WordPress?
Safety Exit’s readme says it’s tested up to WordPress 6.8.12, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
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.