Unused Shortcodes Security & Risk Analysis

wordpress.org/plugins/unused-shortcodes

A plugin to check to see if a shortcode is in use.

10 active installs v1.0.6 PHP + WP 3.1.0+ Updated Oct 28, 2024
admincodeperformanceshortcodeshortcodes
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Unused Shortcodes Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The "unused-shortcodes" v1.0.6 plugin exhibits a generally positive security posture based on the provided static analysis. The plugin has no known CVEs and has not historically had any recorded vulnerabilities, which is a strong indicator of good development practices and a secure codebase. The attack surface is minimal, consisting of only one shortcode, and importantly, there are no unauthenticated entry points, which significantly reduces the risk of unauthorized access or code execution.

However, there are areas for improvement. The most significant concern is the output escaping, where only 33% of outputs are properly escaped. This indicates a potential for Cross-Site Scripting (XSS) vulnerabilities if user-supplied data or dynamically generated content is not properly sanitized before being displayed. While taint analysis did not reveal any critical or high-severity flows, the lack of proper output escaping means that even seemingly innocuous data could be exploited. The absence of nonce checks and capability checks on the shortcode, while not immediately alarming due to the limited attack surface, could become a concern if the shortcode's functionality were to evolve or interact with sensitive data.

In conclusion, the "unused-shortcodes" v1.0.6 plugin is largely secure, especially given its clean vulnerability history and minimal authenticated attack surface. The primary weakness lies in the inconsistent output escaping, which presents a tangible risk of XSS. Addressing this output escaping issue would further solidify the plugin's security. The lack of nonce and capability checks, while not a critical flaw in its current state, is a practice that could be improved for future-proofing.

Key Concerns

  • Low percentage of properly escaped output
Vulnerabilities
None known

Unused Shortcodes Security Vulnerabilities

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

Unused Shortcodes Code Analysis

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

Output Escaping

33% escaped6 total outputs
Attack Surface

Unused Shortcodes Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[unusedshortcodes] unused-shortcodes.php:93
WordPress Hooks 3
actioninitunused-shortcodes.php:33
actionadmin_menuunused-shortcodes.php:38
actionadmin_initunused-shortcodes.php:46
Maintenance & Trust

Unused Shortcodes Maintenance & Trust

Maintenance Signals

WordPress version tested6.1.10
Last updatedOct 28, 2024
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings4
Active installs10
Developer Profile

Unused Shortcodes Developer Profile

AMP-MODE

15 plugins · 13K total installs

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

How We Detect Unused Shortcodes

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/unused-shortcodes/options.php

HTML / DOM Fingerprints

Shortcode Output
<strong>[]</strong>is currently in use in the following page(s)/post(s):No posts found using the shortcode
FAQ

Frequently Asked Questions about Unused Shortcodes