Simple Custom CSS and JS · Security record
Is Simple Custom CSS and JS safe?
No known vulnerability affects the current version (3.55). 1 issue was found in earlier versions and fixed, the latest disclosed on Jul 24, 2017.
Checked 4 days ago against the WPVulnerability database, for version 3.55.
How it’s looked after
- Last release
- Nov 2, 2026 (6 days ago)
- Releases in the last year
- 9
- Tested up to
- WordPress 7.1.4
- Support resolved
- 4 of 7 threads in two months
- Active installs
- 600K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in Simple Custom CSS and JS
Newest first, with any that affect the current version at the top.
- medium
Cross-Site Scripting
Fixed in 3.4 · CVE-2017-2285 · Jul 24, 2017 · Wordfence
Questions about Simple Custom CSS and JS’s security
Is Simple Custom CSS and JS safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Simple Custom CSS and JS updated: most attacks target sites that haven’t updated.
Does Simple Custom CSS and JS have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Simple Custom CSS and JS up to date.
Is Simple Custom CSS and JS still maintained?
Yes. Its last release was 6 days ago. Its authors resolved 4 of the 7 support threads opened in the last two months.
Is Simple Custom CSS and JS 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.