Visual CSS Style Editor · Security record
Is Visual CSS Style Editor safe?
No known vulnerability affects the current version (7.6.7). 6 issues were found in earlier versions and fixed, the latest disclosed on Sep 30, 2024.
Checked 5 days ago against the WPVulnerability database, for version 7.6.7.
How it’s looked after
- Last release
- Aug 23, 2026 (2 months ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 7.1.4
- Active installs
- 30K+
6 known vulnerabilities
- 2 high
- 3 medium
- 1 not rated
None affects the current version.
Disclosed each year
- 20192
- 20221
- 20231
- 20242
Every known vulnerability in Visual CSS Style Editor
Newest first, with any that affect the current version at the top.
Fixed in 7.6.5 · CVE-2024-47348 · Sep 30, 2024 · Wordfence
Fixed in 7.6.4 · CVE-2024-43963 · Aug 26, 2024 · Wordfence
Fixed in 7.5.9 · CVE-2022-33961 · Apr 18, 2023 · Wordfence
Fixed in 7.5.4 · CVE-2021-24934 · Jan 3, 2022 · Wordfence
Fixed in 7.2.1 · Apr 12, 2019 · Patchstack
Fixed in 7.2.1 · CVE-2019-11886 · Apr 11, 2019 · Wordfence
Questions about Visual CSS Style Editor’s security
Is Visual CSS Style Editor safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Visual CSS Style Editor updated: most attacks target sites that haven’t updated.
Does Visual CSS Style Editor have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 6 older issues, fixed in earlier versions, so keep Visual CSS Style Editor up to date.
Is Visual CSS Style Editor still maintained?
Yes. Its last release was 2 months ago. No support threads were opened in the last two months.
Is Visual CSS Style Editor 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.