KM-ShowHide Security & Risk Analysis

wordpress.org/plugins/km-showhide

This simple plugin allows you to toggle your content inside shortcode.

30 active installs v1.01 PHP 5.4+ WP 4.6+ Updated Nov 17, 2019
read-lessread-moreshow-hidetoggle
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is KM-ShowHide Safe to Use in 2026?

Generally Safe

Score 85/100

KM-ShowHide has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 6yr ago
Risk Assessment

The km-showhide plugin version 1.01 demonstrates a strong security posture based on the provided static analysis. The code exhibits excellent practices by exclusively utilizing prepared statements for any SQL queries and ensuring all output is properly escaped, indicating a good defense against common injection vulnerabilities. Furthermore, the absence of dangerous functions, file operations, and external HTTP requests significantly reduces the potential for malicious code execution or data exfiltration. The plugin also benefits from a very small attack surface, with only one shortcode entry point and no identified AJAX handlers, REST API routes, or cron events that are unprotected.

Despite these positive findings, the static analysis does reveal a few areas that, while not currently presenting an immediate threat, warrant attention. The complete absence of nonce checks and capability checks on the sole shortcode entry point represents a missed opportunity for robust access control and potential CSRF protection. While the attack surface is small, this single point of entry lacks the typical WordPress security layers. The vulnerability history shows no known CVEs, which is a significant strength, suggesting that this plugin has historically been secure or not a target. However, this also means there's no historical data to evaluate how the plugin handles security patches or how resistant it has been to past vulnerabilities.

In conclusion, km-showhide v1.01 is in a good security state with a minimal attack surface and strong coding practices for SQL and output handling. The primary weakness lies in the lack of authentication and authorization checks on its shortcode, which, while not exploited in the current analysis, could become a vulnerability if the shortcode's functionality is ever extended to handle sensitive data or actions. The absence of past vulnerabilities is a positive indicator, but the lack of built-in security checks on the shortcode remains the most notable concern.

Key Concerns

  • Shortcode lacks nonce checks
  • Shortcode lacks capability checks
Vulnerabilities
None known

KM-ShowHide Security Vulnerabilities

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

KM-ShowHide Code Analysis

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

KM-ShowHide Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[km_showhide] km-showhide.php:14
WordPress Hooks 1
actionwp_footerkm-showhide.php:24
Maintenance & Trust

KM-ShowHide Maintenance & Trust

Maintenance Signals

WordPress version tested5.3.21
Last updatedNov 17, 2019
PHP min version5.4
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

KM-ShowHide Developer Profile

man_ketan

1 plugin · 30 total installs

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

How We Detect KM-ShowHide

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
read-more-showread-more-contentread-more-hidehide
Shortcode Output
<a class="read-more-show hide" href="#">Read More</a><span class="read-more-content"><a class="read-more-hide hide" href="#">Read Less</a>
FAQ

Frequently Asked Questions about KM-ShowHide