Custom CSS and JavaScript · Security record
Is Custom CSS and JavaScript safe?
One known vulnerability affects the current version (2.0.16), and it has no fix yet.
Checked 5 days ago against the WPVulnerability database, for version 2.0.16.
How it’s looked after
- Last release
- Aug 12, 2024 (2 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.6.11 (current: 7.1)
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 10K+
1 known vulnerability
- 1 medium
1 affects the current version. 1 has no fix yet.
Every known vulnerability in Custom CSS and JavaScript
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2026-66683 · Aug 6, 2026 · Wordfence
Questions about Custom CSS and JavaScript’s security
Is Custom CSS and JavaScript safe to use?
Yes: 1 known vulnerability affects version 2.0.16, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Custom CSS and JavaScript have known security vulnerabilities?
Yes: 1 known vulnerability affects version 2.0.16, according to WPVulnerability’s database.
Is Custom CSS and JavaScript still maintained?
Its last release was 2 years ago, so it may no longer be actively maintained. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Custom CSS and JavaScript compatible with the latest WordPress?
Custom CSS and JavaScript’s readme says it’s tested up to WordPress 6.6.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.