Legacy Jetpack Custom CSS Editor Security & Risk Analysis

wordpress.org/plugins/legacy-jetpack-custom-css-editor

This plugin re-adds the full page admin Custom CSS editor to Jetpack.

20 active installs v0.9 PHP + WP 4.7+ Updated Dec 16, 2016
custom-cssjetpack
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Legacy Jetpack Custom CSS Editor Safe to Use in 2026?

Generally Safe

Score 85/100

Legacy Jetpack Custom CSS Editor has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9yr ago
Risk Assessment

The legacy-jetpack-custom-css-editor plugin version 0.9 exhibits a generally strong security posture based on the provided static analysis. The absence of dangerous functions, SQL injection risks due to prepared statements, and minimal external requests are positive indicators. Furthermore, the plugin demonstrates good practices with a high percentage of properly escaped output and the presence of nonce and capability checks on its entry points. The vulnerability history is also entirely clean, with no known CVEs, which suggests a well-maintained or less targeted plugin.

Despite these strengths, the analysis does reveal a single AJAX handler as the sole entry point. While it has an apparent authentication check, the static analysis does not detail the specifics of this check. The total lack of taint analysis results could be due to the limited complexity of the plugin or limitations in the analysis tool's scope for this specific plugin. However, it means there's no specific insight into potential data flow vulnerabilities. Overall, the plugin appears relatively secure, but the reliance on a single AJAX handler warrants careful review of its authentication mechanism.

Vulnerabilities
None known

Legacy Jetpack Custom CSS Editor Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

Legacy Jetpack Custom CSS Editor Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
2
16 escaped
Nonce Checks
2
Capability Checks
3
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

89% escaped18 total outputs
Attack Surface

Legacy Jetpack Custom CSS Editor Attack Surface

Entry Points1
Unprotected0

AJAX Handlers 1

authwp_ajax_legacy_jetpack_preview_custom_csslegacy-jetpack-custom-css-editor.php:30
WordPress Hooks 3
actionadmin_menulegacy-jetpack-custom-css-editor.php:27
actionadmin_initlegacy-jetpack-custom-css-editor.php:28
actionadmin_post_legacy_jetpack_update_custom_csslegacy-jetpack-custom-css-editor.php:29
Maintenance & Trust

Legacy Jetpack Custom CSS Editor Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedDec 16, 2016
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings2
Active installs20
Developer Profile

Legacy Jetpack Custom CSS Editor Developer Profile

George Stephanis

16 plugins · 16K total installs

84
trust score
Avg Security Score
86/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Legacy Jetpack Custom CSS Editor

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/legacy-jetpack-custom-css-editor/use-codemirror.js/wp-content/plugins/legacy-jetpack-custom-css-editor/no-jetpack.js
Script Paths
/wp-content/plugins/legacy-jetpack-custom-css-editor/use-codemirror.js/wp-content/plugins/legacy-jetpack-custom-css-editor/no-jetpack.js
Version Parameters
legacy-jetpack-custom-css-editor/use-codemirror.js?ver=0.1-dev

HTML / DOM Fingerprints

Data Attributes
id="legacy-form"name="css"name="jetpack_custom_css[preprocessor]"name="jetpack_custom_css[replace]"name="jetpack_custom_css[content_width]"
FAQ

Frequently Asked Questions about Legacy Jetpack Custom CSS Editor