TwoSides Security & Risk Analysis

wordpress.org/plugins/twosides

Split comments into two types of commenting groups.

0 active installs v1.1.0 PHP 5.6+ WP 4.4+ Updated Apr 13, 2023
commentsopinionspro-conreviewssplit-comments
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is TwoSides Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 3yr ago
Risk Assessment

The "twosides" plugin v1.1.0 exhibits a generally strong security posture based on the provided static analysis. The absence of dangerous functions, all SQL queries utilizing prepared statements, and a high percentage of properly escaped output are excellent indicators of secure coding practices. Furthermore, the presence of nonce and capability checks, coupled with zero external HTTP requests or file operations, significantly reduces the potential attack surface. The plugin also boasts a clean vulnerability history with no known CVEs, suggesting a history of stability and security awareness.

However, it's important to note that the analysis did not uncover any taint flows, which could imply either a lack of complex data handling or a limitation in the static analysis tool's ability to detect certain types of vulnerabilities. The sole entry point, a shortcode, is not explicitly stated as being protected by authentication checks in the 'Unprotected' count. While the total entry points are low, this specific shortcode's implementation should be thoroughly reviewed to ensure it doesn't introduce vulnerabilities if it handles user-supplied data without proper sanitization or capability checks.

In conclusion, "twosides" v1.1.0 appears to be a well-developed plugin from a security perspective, with a strong emphasis on preventing common vulnerabilities. The low number of entry points and the robust implementation of security features are commendable. The main area for vigilance would be the specific implementation of the single shortcode to confirm it's adequately secured against potential misuse.

Key Concerns

  • Shortcode entry point without explicit auth check noted
Vulnerabilities
None known

TwoSides Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

TwoSides Release Timeline

v1.1.0Current
v1.0.5
v1.0.4
v1.0.3
v1.0.2
Code Analysis
Analyzed Apr 16, 2026

TwoSides Code Analysis

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

Output Escaping

92% escaped200 total outputs
Attack Surface

TwoSides Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[twosides_form_header] twosides.php:119
WordPress Hooks 18
actionadmin_menuincludes/twosides-debate-admin-settings.php:12
actionadmin_initincludes/twosides-debate-admin-settings.php:13
filtercomment_post_redirectincludes/twosides-debate-functions.php:12
filterpreprocess_commentincludes/twosides-debate-functions.php:14
actionwp_enqueue_scriptsincludes/twosides-debate-functions.php:18
actioncomment_form_after_fieldsincludes/twosides-debate-functions.php:20
actioncomment_postincludes/twosides-debate-functions.php:22
actiontwosides_debate_comment_formincludes/twosides-debate-functions.php:24
actiontwosides_debate_before_comment_listincludes/twosides-debate-functions.php:26
actiontwosides_debate_debug_infoincludes/twosides-debate-functions.php:28
actionadd_meta_boxesincludes/twosides-debate-helpers.php:9
actionedit_commentincludes/twosides-debate-helpers.php:11
filtercomments_templatetemplates/twosides-comments_templater.php:12
filtercomments_templatetemplates/twosides-debate-comments_templater.php:12
actionwp_enqueue_scriptstwosides.php:60
actionadmin_enqueue_scriptstwosides.php:95
actioninittwosides.php:110
actionshutdowntwosides.php:134
Maintenance & Trust

TwoSides Maintenance & Trust

Maintenance Signals

WordPress version tested6.2.9
Last updatedApr 13, 2023
PHP min version5.6
Downloads852

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

TwoSides Developer Profile

tradesouthwest

19 plugins · 2K total installs

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

How We Detect TwoSides

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/twosides/library/twosides-debate-css.css/wp-content/plugins/twosides/library/twosides-debate-admin-css.css/wp-content/plugins/twosides/library/twosides-debate-plugin.js/wp-content/plugins/twosides/library/twosides-debate-colors.js
Script Paths
/wp-content/plugins/twosides/library/twosides-debate-plugin.js/wp-content/plugins/twosides/library/twosides-debate-colors.js
Version Parameters
twosides-debate-css?ver=twosides-debate-admin-css?ver=twosides-debate-plugin?ver=twosides-debate-colors?ver=

HTML / DOM Fingerprints

CSS Classes
twosides-debate-comment
HTML Comments
<!-- @id F2 --><!-- @id F5 --><!-- @id A1 --><!-- @id A7 -->+12 more
Data Attributes
twosides_commtype
JS Globals
twosides_debate_debug_class
Shortcode Output
[twosides_form_header]
FAQ

Frequently Asked Questions about TwoSides