CVE-2025-54722

7.1 HIGH

📋 TL;DR

This vulnerability allows attackers to inject malicious scripts into WooTour plugin pages, which execute in victims' browsers when they visit specially crafted URLs. It affects WordPress sites using WooTour plugin versions up to and including 3.6.3. The vulnerability is reflected XSS, meaning the malicious script comes from the current HTTP request.

💻 Affected Systems

Products:
  • Ex-Themes WooTour (WordPress plugin)
Versions: All versions up to and including 3.6.3
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with WooTour plugin enabled. The vulnerability exists in the plugin's web page generation code.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, redirect users to malicious sites, deface websites, or perform actions on behalf of authenticated users if combined with other vulnerabilities.

🟠

Likely Case

Attackers typically use this to steal session cookies or credentials, redirect users to phishing pages, or display malicious content to users.

🟢

If Mitigated

With proper input validation and output encoding, the malicious scripts would be neutralized before reaching users' browsers.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

XSS vulnerabilities are commonly weaponized in phishing campaigns and drive-by attacks. The Patchstack reference provides technical details.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version after 3.6.3

Vendor Advisory: https://patchstack.com/database/Wordpress/Plugin/woo-tour/vulnerability/wordpress-wootour-plugin-3-6-3-cross-site-scripting-xss-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Go to Plugins → Installed Plugins. 3. Find WooTour plugin. 4. Click 'Update Now' if update available. 5. If no update available, deactivate and remove plugin until patch is released.

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize user inputs before processing

Add sanitization functions like esc_html(), esc_attr(), or wp_kses() to plugin code where user input is processed

Content Security Policy

all

Implement CSP headers to restrict script execution sources

Add header: Content-Security-Policy: script-src 'self' https://trusted.cdn.com;

🧯 If You Can't Patch

  • Disable or remove WooTour plugin immediately
  • Implement web application firewall (WAF) rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for WooTour version. If version is 3.6.3 or lower, you are vulnerable.

Check Version:

wp plugin list --name=woo-tour --field=version (if WP-CLI installed)

Verify Fix Applied:

After updating, verify WooTour version is higher than 3.6.3 in WordPress plugins list.

📡 Detection & Monitoring

Log Indicators:

  • Unusual long URLs with script tags in access logs
  • Multiple failed requests with XSS payload patterns

Network Indicators:

  • HTTP requests containing <script>, javascript:, or eval() patterns
  • Unusual redirects from WooTour pages

SIEM Query:

source="web_access_logs" AND (uri="*<script>*" OR uri="*javascript:*") AND uri="*woo-tour*"

🔗 References

📤 Share & Export