Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesVisual CSS Style Editor

Visual CSS Style Editor vulnerabilities

Visual CSS Style Editor has 3 known vulnerabilities in this database. The most recent published record is dated 22 Nov 2026.

Known vulnerabilities
3
Active installs
30,000+
Latest version
7.6.7
Last updated
23 Aug 2026
Most recent
22 Nov 2026

No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Cross-site scripting (XSS)
CVE-2026-131794
High 7.1Up to 7.6.7No fixed version yet6 h ago
Cross-site scripting (XSS)
CVE-2021-24934
Medium 6.1Before 7.5.4Fixed in 7.5.41 Feb 2022
Cross-site request forgery (CSRF)
CVE-2019-11886
High 8.8Before 7.2.1Fixed in 7.2.113 May 2019
Read the published descriptions
CVE-2026-131794, 22 Nov 2026
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in YellowPencil YellowPencil Visual CSS Style Editor yellow-pencil-visual-theme-customizer allows Reflected XSS.This issue affects YellowPencil Visual CSS Style Editor: from n/a through 7.6.7. CVE record
CVE-2021-24934, 1 Feb 2022
The Visual CSS Style Editor WordPress plugin before 7.5.4 does not sanitise and escape the wyp_page_type parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting issue CVE record
CVE-2019-11886, 13 May 2019
The WaspThemes Visual CSS Style Editor (aka yellow-pencil-visual-theme-customizer) plugin before 7.2.1 for WordPress allows yp_option_update CSRF, as demonstrated by use of yp_remote_get to obtain admin access. CVE record

What to do if you run Visual CSS Style Editor

If you run Visual CSS Style Editor, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.

If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.

Email me about new Visual CSS Style Editor vulnerabilities

Free. We email you when a new vulnerability is published for Visual CSS Style Editor, usually within minutes. Confirm by email; unsubscribe any time.

Focus on your business. We’ll take care of your website.

From everyday updates to ongoing care, we keep your website working.

Get website support