Relevanssi · Security record
Is Relevanssi safe?
No known vulnerability affects the current version (4.28.8). 33 issues were found in earlier versions and fixed, the latest disclosed on Oct 22, 2026.
Checked 5 days ago against the WPVulnerability database, for version 4.28.8.
How it’s looked after
- Last release
- Oct 30, 2026 (1 week ago)
- Releases in the last year
- 14
- Tested up to
- WordPress 7.1.4
- Support resolved
- 10 of 15 threads in two months
- Active installs
- 100K+
33 known vulnerabilities
- 1 critical
- 6 high
- 10 medium
- 16 not rated
None affects the current version.
Disclosed each year
- 20111
- 20142
- 20152
- 20171
- 20182
- 20212
- 20222
- 20246
- 20254
- 20265
Every known vulnerability in Relevanssi
Newest first, with any that affect the current version at the top.
Fixed in 4.28.6 · CVE-2026-116522 · Oct 22, 2026 · Wordfence
Fixed in 4.28.5 · CVE-2026-114704 · Oct 1, 2026 · Wordfence
Fixed in 4.28.4 · CVE-2026-97641 · Sep 10, 2026 · Wordfence
Fixed in 4.28.2 · CVE-2026-19985 · Aug 4, 2026 · Wordfence
Fixed in 4.27.2 · CVE-2026-15941 · Aug 4, 2026 · Wordfence
Fixed in 4.26.0 · CVE-2025-14719 · Dec 17, 2025 · Wordfence
Fixed in 4.24.6 · CVE-2025-5016 · May 30, 2025 · Wordfence
Fixed in 4.24.5 · CVE-2025-4396 · May 12, 2025 · Wordfence
Fixed in 4.24.4 · CVE-2025-4054 · May 6, 2025 · Wordfence
Fixed in 4.23.1 · CVE-2024-9021 · Sep 17, 2024 · Wordfence
Fixed in 4.23.0 · CVE-2024-7630 · Aug 15, 2024 · Wordfence
Fixed in 4.22.2 · CVE-2024-3213 · Apr 4, 2024 · Wordfence
Fixed in 4.22.2 · CVE-2024-3214 · Apr 4, 2024 · Wordfence
Fixed in 4.22.1 · CVE-2024-1380 · Feb 22, 2024 · Wordfence
Fixed in 4.22.0 · CVE-2023-7199 · Jan 4, 2024 · Wordfence
Fixed in 4.14.6 · Feb 15, 2022 · Wordfence
Fixed in 4.14.6 · Feb 15, 2022 · Patchstack
Fixed in 4.14.4 · Oct 19, 2021 · Wordfence
Fixed in 4.14.3 · Oct 19, 2021 · Patchstack
Fixed in 3.6.1 · Apr 10, 2018 · Wordfence
- medium
Cross-Site Scripting
Fixed in 4.0.5 · CVE-2018-9034 · Mar 30, 2018 · Wordfence
Fixed in 3.5.8 · CVE-2017-1000038 · Feb 28, 2017 · Wordfence
Fixed in 3.3 · May 15, 2015 · Patchstack
Fixed in 3.3.8 · CVE-2014-9443 · Jan 2, 2015 · Wordfence
Fixed in 3.4 · Mar 4, 2014 · Patchstack
Fixed in 3.3.1 · Feb 25, 2014 · Wordfence
Fixed in 2.7.3 · Feb 24, 2011 · Patchstack
Fixed in 4.22 · Patchstack
Fixed in 3.3 · WPScan
Fixed in 2.7.3 · WPScan
Fixed in 3.6.1 · WPScan
Fixed in 4.14.3 · WPScan
Fixed in 4.14.6 · WPScan
Questions about Relevanssi’s security
Is Relevanssi safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Relevanssi updated: most attacks target sites that haven’t updated.
Does Relevanssi have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 33 older issues, fixed in earlier versions, so keep Relevanssi up to date.
Is Relevanssi still maintained?
Yes. Its last release was 1 week ago. Its authors resolved 10 of the 15 support threads opened in the last two months.
Is Relevanssi 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.