Classic Addons · Security record
Is Classic Addons safe?
No known vulnerability affects the current version (4.3). 3 issues were found in earlier versions and fixed, the latest disclosed on Jan 3, 2025.
Checked 5 days ago against the WPVulnerability database, for version 4.3.
How it’s looked after
- Last release
- Sep 18, 2026 (1 month ago)
- Releases in the last year
- 5
- Tested up to
- WordPress 7.1.4
- Support resolved
- 0 of 2 threads in two months
- Active installs
- 3K+
3 known vulnerabilities
- 2 high
- 1 medium
None affects the current version.
Disclosed each year
- 20242
- 20251
Every known vulnerability in Classic Addons
Newest first, with any that affect the current version at the top.
Fixed in 3.1 · CVE-2024-56286 · Jan 3, 2025 · Wordfence
Fixed in 3.1 · CVE-2024-11952 · Dec 3, 2024 · Wordfence
Fixed in 3.6 · CVE-2024-43953 · Aug 26, 2024 · Wordfence
Questions about Classic Addons’s security
Is Classic Addons safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Classic Addons updated: most attacks target sites that haven’t updated.
Does Classic Addons have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 3 older issues, fixed in earlier versions, so keep Classic Addons up to date.
Is Classic Addons still maintained?
Yes. Its last release was 1 month ago. Its authors resolved 0 of the 2 support threads opened in the last two months.
Is Classic Addons 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.