BEW · Security record
Is BEW safe?
No known vulnerability affects the current version (2.1.3). 1 issue was found in earlier versions and fixed, the latest disclosed on Jun 6, 2024.
Checked 3 days ago against the WPVulnerability database, for version 2.1.3.
How it’s looked after
- Last release
- Oct 12, 2026 (4 weeks ago)
- Releases in the last year
- 9
- Tested up to
- WordPress 7.1.4
- Active installs
- 20K+
1 known vulnerability
- 1 high
None affects the current version.
Every known vulnerability in BEW
Newest first, with any that affect the current version at the top.
Fixed in 1.0.13 · CVE-2024-35724 · Jun 6, 2024 · Wordfence
Questions about BEW’s security
Is BEW safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep BEW updated: most attacks target sites that haven’t updated.
Does BEW have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep BEW up to date.
Is BEW still maintained?
Yes. Its last release was 4 weeks ago. No support threads were opened in the last two months.
Is BEW 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.