WP Accordion Security & Risk Analysis

wordpress.org/plugins/my-wp-accordion

This plugin will add an expand collapse accordion feature inside a post or page.

10 active installs v1.1 PHP + WP 3.0.1+ Updated Feb 20, 2017
accordionjquery-accordion
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Accordion Safe to Use in 2026?

Generally Safe

Score 85/100

WP Accordion 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 'my-wp-accordion' v1.1 plugin exhibits a strong security posture based on the provided static analysis. The absence of dangerous functions, proper use of prepared statements for any SQL queries, and complete output escaping are commendable practices. Furthermore, the plugin's minimal attack surface, with no unprotected AJAX handlers or REST API routes, significantly reduces the immediate risk of common web vulnerabilities. The lack of any recorded vulnerabilities in its history is also a positive indicator of its development and maintenance quality.

However, a critical area of concern is the complete absence of nonce and capability checks for its two shortcodes. While the static analysis doesn't reveal any exploitable taint flows or direct SQL injection vulnerabilities, these shortcodes represent potential entry points that are not protected against unauthorized access or privilege escalation. If these shortcodes perform any actions that modify data or display user-specific content, their lack of proper authorization checks could lead to security issues. The plugin's strength lies in its lack of known vulnerabilities and secure coding practices for data handling, but the unprotected shortcodes are a notable weakness.

In conclusion, 'my-wp-accordion' v1.1 appears to be a securely coded plugin concerning data manipulation and output. The absence of known vulnerabilities is reassuring. The primary and significant risk stems from the unprotected shortcodes, which are potential vectors for cross-site request forgery (CSRF) or unauthorized data access/modification if they interact with sensitive backend functionality. Addressing these unprotected entry points should be the priority to achieve a more robust security profile.

Key Concerns

  • Shortcodes lack nonce and capability checks
Vulnerabilities
None known

WP Accordion Security Vulnerabilities

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

WP Accordion 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

WP Accordion Attack Surface

Entry Points2
Unprotected0

Shortcodes 2

[wp_accordion] plugin-hook.php:65
[wp_toggle] plugin-hook.php:81
WordPress Hooks 4
actionwp_enqueue_scriptsplugin-hook.php:35
filtermce_external_pluginsplugin-hook.php:43
filtermce_buttonsplugin-hook.php:44
actioninitplugin-hook.php:56
Maintenance & Trust

WP Accordion Maintenance & Trust

Maintenance Signals

WordPress version tested4.0.38
Last updatedFeb 20, 2017
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

WP Accordion Developer Profile

Sohelwpexpert

10 plugins · 190 total installs

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

How We Detect WP Accordion

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/my-wp-accordion/css/style.css/wp-content/plugins/my-wp-accordion/js/florida-custom.js
Script Paths
/wp-content/plugins/my-wp-accordion/js/accordian-button.js

HTML / DOM Fingerprints

CSS Classes
acc-triggeracc-containercontent
Shortcode Output
<div id="wp-tabs"><span class="acc-trigger active"><a href="#"><strong></strong></a></span><div class="acc-container">
FAQ

Frequently Asked Questions about WP Accordion