Theme Support Security & Risk Analysis

wordpress.org/plugins/theme-support

Quickly config theme support using UI

50 active installs v0.1.1 PHP + WP 3.0.1+ Updated Nov 21, 2018
editorgutenbergsupporttheme
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Theme Support Safe to Use in 2026?

Generally Safe

Score 85/100

Theme Support has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 7yr ago
Risk Assessment

The 'theme-support' plugin v0.1.1 exhibits a generally strong security posture in terms of its attack surface and known vulnerability history. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits potential entry points for attackers. Furthermore, the plugin demonstrates good practice by utilizing prepared statements for all its SQL queries and shows no history of known vulnerabilities, suggesting diligent development and maintenance regarding known exploits.

However, a critical concern arises from the output escaping analysis. With 2 total outputs and 0% properly escaped, this indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities. Any user-provided or dynamically generated content that is not properly escaped before being displayed to users can be exploited by attackers to inject malicious scripts. The lack of capability checks and nonce checks, while not directly flagged as exploitable given the zero attack surface, would become significant risks if any entry points were to be introduced or discovered in future versions without proper safeguards.

In conclusion, while the plugin avoids common pitfalls like unpatched CVEs and raw SQL queries, the severe lack of output escaping represents a substantial and immediate security risk. Addressing this issue is paramount to securing the plugin against potential XSS attacks. The absence of other security checks like nonces and capabilities is a latent risk that should be monitored and rectified if the plugin's functionality expands.

Key Concerns

  • Unescaped output (2 outputs, 0% escaped)
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

Theme Support Security Vulnerabilities

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

Theme Support Code Analysis

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

Output Escaping

0% escaped2 total outputs
Attack Surface

Theme Support Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actioninitwp-theme-support.php:80
actioninitwp-theme-support.php:81
actionenqueue_block_editor_assetswp-theme-support.php:82
actionafter_setup_themewp-theme-support.php:83
actionadmin_headwp-theme-support.php:84
actionwp_headwp-theme-support.php:85
Maintenance & Trust

Theme Support Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedNov 21, 2018
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs50
Developer Profile

Theme Support Developer Profile

lubus

8 plugins · 600 total installs

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

How We Detect Theme Support

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/theme-support/build/script.js/wp-content/plugins/theme-support/build/style.css
Script Paths
/wp-content/plugins/theme-support/build/script.js

HTML / DOM Fingerprints

Data Attributes
data-align="wide"data-align="full"
REST Endpoints
/wp-json/lubusin-theme-support/v1/settings
FAQ

Frequently Asked Questions about Theme Support