Better Search Replace · Security record
Is Better Search Replace safe?
No known vulnerability affects the current version (1.4.11). 2 issues were found in earlier versions and fixed, the latest disclosed on Jan 24, 2024.
Checked 4 days ago against the WPVulnerability database, for version 1.4.11.
How it’s looked after
- Last release
- Aug 25, 2026 (2 months ago)
- Releases in the last year
- 2
- Tested up to
- WordPress 7.1.4
- Support resolved
- 0 of 3 threads in two months
- Active installs
- 1M+
2 known vulnerabilities
- 1 critical
- 1 high
None affects the current version.
Disclosed each year
- 20221
- 20241
Every known vulnerability in Better Search Replace
Newest first, with any that affect the current version at the top.
Fixed in 1.4.5 · CVE-2023-6933 · Jan 24, 2024 · Wordfence
Fixed in 1.4.1 · CVE-2022-2593 · Aug 1, 2022 · Wordfence
Questions about Better Search Replace’s security
Is Better Search Replace safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Better Search Replace updated: most attacks target sites that haven’t updated.
Does Better Search Replace have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep Better Search Replace up to date.
Is Better Search Replace still maintained?
Yes. Its last release was 2 months ago. Its authors resolved 0 of the 3 support threads opened in the last two months.
Is Better Search Replace 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.