Conditional Lightbox Security & Risk Analysis

wordpress.org/plugins/conditional-lightbox

Use a lightbox only if the screen is big enough.

10 active installs v1.0 PHP + WP 2.7+ Updated Unknown
androidipadiphonelightboxmobile
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Conditional Lightbox Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The conditional-lightbox plugin v1.0 presents a mixed security posture. On the positive side, the static analysis reveals no dangerous functions, no unescaped file operations, no external HTTP requests, and all SQL queries appear to be properly prepared. Furthermore, the plugin has no recorded vulnerability history, suggesting a historically clean record. However, a significant concern arises from the complete lack of output escaping for all four identified output points. This indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities, as user-supplied data could potentially be injected into these outputs without proper sanitization, leading to arbitrary code execution in the user's browser.

While the attack surface is currently zero and there are no identified taint flows or unpatched CVEs, the unescaped output remains a critical oversight. The absence of capability checks and nonce checks on any potential entry points, though currently zero, also leaves room for concern if the plugin were to evolve and introduce new functionalities without these fundamental security measures. In conclusion, the plugin benefits from a clean history and absence of many common vulnerabilities, but the unescaped output is a serious and actionable security flaw that requires immediate attention to mitigate XSS risks.

Key Concerns

  • 0% output escaping
Vulnerabilities
None known

Conditional Lightbox Security Vulnerabilities

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

Conditional Lightbox Code Analysis

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

Output Escaping

0% escaped4 total outputs
Attack Surface

Conditional Lightbox Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actionadmin_initconditional-lightbox.php:31
actionadmin_menuconditional-lightbox.php:32
filterplugin_action_linksconditional-lightbox.php:33
actionwp_footerconditional-lightbox.php:172
actioninitconditional-lightbox.php:175
Maintenance & Trust

Conditional Lightbox Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating60/100
Number of ratings2
Active installs10
Developer Profile

Conditional Lightbox Developer Profile

Stefan Matei

2 plugins · 20 total installs

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

How We Detect Conditional Lightbox

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/conditional-lightbox/images/facebook-icon.png/wp-content/plugins/conditional-lightbox/images/twitter-icon.png
Script Paths
/conditional-lightbox/slimbox-2.04/js/slimbox2.js
Version Parameters
conditional-lightbox/slimbox-2.04/js/slimbox2.js?ver=1.0

HTML / DOM Fingerprints

HTML Comments
<!-- Display Plugin Icon, Header, and Description --><!-- Beginning of the Plugin Options Form --><!-- Table Structure Containing Form Controls --><!-- Each Plugin Option Defined on a New Table Row -->+4 more
Data Attributes
name="coli_options[txt_width]"
FAQ

Frequently Asked Questions about Conditional Lightbox