CVE-2025-3745

6.3 MEDIUM

📋 TL;DR

This vulnerability in the WP Lightbox 2 WordPress plugin allows attackers to inject malicious scripts via unsanitized title attributes, leading to cross-site scripting (XSS) attacks. WordPress sites using vulnerable versions of this plugin are affected, potentially compromising visitor sessions and site integrity.

💻 Affected Systems

Products:
  • WP Lightbox 2 WordPress Plugin
Versions: All versions before 3.0.6.8
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with the WP Lightbox 2 plugin enabled. The vulnerability requires user interaction (clicking a malicious link).

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, deface websites, redirect visitors to malicious sites, or install backdoors for persistent access.

🟠

Likely Case

Attackers inject malicious JavaScript to steal user session cookies, perform actions on behalf of users, or display phishing content.

🟢

If Mitigated

With proper input validation and output encoding, the attack surface is minimized, though the vulnerability still exists in the codebase.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

XSS vulnerabilities in WordPress plugins are commonly exploited. The WPScan reference provides technical details that could be used to create exploits.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.0.6.8

Vendor Advisory: https://wpscan.com/vulnerability/1b50f686-c2e0-4963-95c8-b27137dcc059/

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find WP Lightbox 2 and click 'Update Now'. 4. Verify the plugin version is 3.0.6.8 or higher.

🔧 Temporary Workarounds

Disable WP Lightbox 2 Plugin

all

Temporarily disable the vulnerable plugin until patching is possible

wp plugin deactivate wp-lightbox-2

Implement Content Security Policy

all

Add CSP headers to mitigate XSS impact by restricting script execution

Add to .htaccess: Header set Content-Security-Policy "default-src 'self'; script-src 'self'"
Add to wp-config.php: header("Content-Security-Policy: default-src 'self'; script-src 'self'");

🧯 If You Can't Patch

  • Disable the WP Lightbox 2 plugin immediately
  • Implement web application firewall (WAF) rules to block XSS payloads in title parameters

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Installed Plugins for WP Lightbox 2 version number

Check Version:

wp plugin get wp-lightbox-2 --field=version

Verify Fix Applied:

Verify plugin version is 3.0.6.8 or higher in WordPress admin panel

📡 Detection & Monitoring

Log Indicators:

  • Unusual JavaScript in URL parameters containing title attributes
  • Multiple requests to wp-lightbox-2 endpoints with suspicious payloads

Network Indicators:

  • HTTP requests containing script tags or JavaScript in title parameters
  • Unusual outbound connections from WordPress site after visiting links

SIEM Query:

source="wordpress" AND (uri="*wp-lightbox-2*" AND (param="*title*" AND value="*<script>*"))

🔗 References

📤 Share & Export