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