Is Custom Style safe to use?

Laskyr does not give safety verdicts. The latest version (1.0) has 1 known unpatched vulnerability. As of 2026-11-04, the sources we check list the newest release of Custom Style as affected and name no fixed version yet. Keep Custom Style on the latest version (1.0) and remove it if you do not use it.

Which versions of Custom Style are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (1.0 and older). The full list with sources is on this page.

What is the latest version of Custom Style?

1.0, according to wordpress.org (last updated 2010-02-25). It has 30+ active installs.

What should I do if my Custom Style is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update custom-style). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · custom-style · data as of 2026-11-04

Is Custom Style safe? Known vulnerabilities and latest version

Latest version: 1.0
Last updated: 2010-02-25
Active installs: 30+
Known issues on record: 1
Unpatched in latest: 1
Tested up to WP: 2.9.2

A simple plugin allowing you to add some CSS rules to customize your theme to your liking. — by merzedes

What to do

There is no fixed version yet. If you can live without Custom Style for now, deactivate it and delete it until the developer ships a fix.
If you must keep it, limit who can log in (remove unused accounts, especially low-level ones) and put a web application firewall in front of the site.
Watch for an update: get an email when this page changes.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI: wp plugin get custom-style --field=version shows what you run; wp plugin update custom-style updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.1 affects latest 1.0 CVE-2025-49342 · published 2025-12-31

Cross-site request forgery (CSRF) in Custom Style (1.0 and older)

Affected: 1.0 and older
Fixed in: no fix listed yet
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in merzedes Custom Style custom-style allows Stored XSS.This issue affects Custom Style: from n/a through <= 1.0.

NVD CVE-2025-49342 Patchstack advisory

Recent activity

2010-02-25 — latest release on wordpress.org (1.0).
2025-12-31 — Cross-site request forgery (CSRF) disclosed (CVE-2025-49342), no fix listed yet.

Free. We check the CVE feeds every day and email you only when a new issue for Custom Style (custom-style) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site request forgery (CSRF) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/custom-style (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/custom-style"><img src="https://laskyr.com/plugins/custom-style/badge.svg" alt="Custom Style vulnerability status"></a>

← Check another plugin · Free hacked-site scan