Add Custom Codes · Security record
Is Add Custom Codes safe?
No known vulnerability affects the current version (5.0). 4 issues were found in earlier versions and fixed, the latest disclosed on Dec 31, 2025.
Checked today against the WPVulnerability database, for version 5.0.
How it’s looked after
- Last release
- May 22, 2026 (5 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 7.0.8
- Active installs
- 1K+
4 known vulnerabilities
- 1 high
- 1 medium
- 2 not rated
None affects the current version.
Every known vulnerability in Add Custom Codes
Newest first, with any that affect the current version at the top.
Fixed in 5.0 · CVE-2025-62149 · Dec 31, 2025 · Wordfence
Fixed in 5.0 · CVE-2025-62108 · Dec 31, 2025 · Wordfence
Fixed in 5.0 · CVE-2025-62739 · Dec 5, 2025 · Wordfence
Fixed in 5.0 · CVE-2025-30975 · Aug 14, 2025 · Wordfence
Questions about Add Custom Codes’s security
Is Add Custom Codes safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Add Custom Codes updated: most attacks target sites that haven’t updated.
Does Add Custom Codes have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep Add Custom Codes up to date.
Is Add Custom Codes still maintained?
Yes. Its last release was 5 months ago. No support threads were opened in the last two months.
Is Add Custom Codes compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
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.