Web Accessibility by accessiBe · Security record
Is Web Accessibility by accessiBe safe?
No known vulnerability affects the current version (2.13). 6 issues were found in earlier versions and fixed, the latest disclosed on Feb 18, 2026.
Checked 4 days ago against the WPVulnerability database, for version 2.13.
How it’s looked after
- Last release
- Feb 23, 2026 (8 months ago)
- Releases in the last year
- 2
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Active installs
- 10K+
6 known vulnerabilities
- 1 high
- 3 medium
- 2 not rated
None affects the current version.
Disclosed each year
- 20232
- 20253
- 20261
Every known vulnerability in Web Accessibility by accessiBe
Newest first, with any that affect the current version at the top.
Fixed in 2.12 · CVE-2025-13113 · Feb 18, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 2.11 · CVE-2025-49920 · Oct 22, 2025 · Wordfence
Fixed in 2.11 · CVE-2025-10375 · Oct 10, 2025 · Wordfence
Fixed in 2.6 · CVE-2025-26981 · Feb 23, 2025 · Wordfence
Fixed in 1.16 · Jul 28, 2023 · Patchstack
Fixed in 1.16 · Jul 27, 2023 · Wordfence
Questions about Web Accessibility by accessiBe’s security
Is Web Accessibility by accessiBe safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Web Accessibility by accessiBe updated: most attacks target sites that haven’t updated.
Does Web Accessibility by accessiBe have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 6 older issues, fixed in earlier versions, so keep Web Accessibility by accessiBe up to date.
Is Web Accessibility by accessiBe still maintained?
Its last release was 8 months ago. No support threads were opened in the last two months.
Is Web Accessibility by accessiBe compatible with the latest WordPress?
Web Accessibility by accessiBe’s readme says it’s tested up to WordPress 6.9.11, 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.