CVE-2025-67537

6.5 MEDIUM

📋 TL;DR

This stored cross-site scripting (XSS) vulnerability in the ThirstyAffiliates WordPress plugin allows attackers to inject malicious scripts into web pages that are then executed when other users view those pages. It affects all WordPress sites running ThirstyAffiliates version 3.11.8 or earlier. Attackers could steal session cookies, redirect users to malicious sites, or perform actions on behalf of authenticated users.

💻 Affected Systems

Products:
  • ThirstyAffiliates WordPress Plugin
Versions: All versions up to and including 3.11.8
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with ThirstyAffiliates plugin installed and activated.

⚠️ 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

An attacker could steal administrator session cookies, take over the WordPress site, install backdoors, deface the site, or pivot to attack other systems in the network.

🟠

Likely Case

Attackers steal user session cookies, redirect visitors to phishing/malware sites, or perform unauthorized actions on behalf of logged-in users.

🟢

If Mitigated

With proper input validation and output encoding, the malicious scripts would be rendered harmless as text rather than executable code.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Stored XSS vulnerabilities are commonly exploited. While no public PoC exists, the vulnerability type is well-understood and easy to weaponize.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.11.9 or later

Vendor Advisory: https://patchstack.com/database/Wordpress/Plugin/thirstyaffiliates/vulnerability/wordpress-thirstyaffiliates-plugin-3-11-8-cross-site-scripting-xss-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find ThirstyAffiliates and click 'Update Now'. 4. Alternatively, download version 3.11.9+ from WordPress.org and manually replace the plugin files.

🔧 Temporary Workarounds

Disable ThirstyAffiliates Plugin

all

Temporarily disable the vulnerable plugin until patched

wp plugin deactivate thirstyaffiliates

Implement Content Security Policy

all

Add CSP headers to restrict script execution sources

Add to .htaccess: Header set Content-Security-Policy "default-src 'self'; script-src 'self'"
Add to nginx config: add_header Content-Security-Policy "default-src 'self'; script-src 'self'";

🧯 If You Can't Patch

  • Implement a Web Application Firewall (WAF) with XSS protection rules
  • Restrict plugin access to trusted users only and monitor for suspicious activity

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for ThirstyAffiliates version number

Check Version:

wp plugin get thirstyaffiliates --field=version

Verify Fix Applied:

Verify ThirstyAffiliates version is 3.11.9 or higher in WordPress admin panel

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to ThirstyAffiliates endpoints containing script tags
  • Multiple failed XSS attempts in web server logs
  • Suspicious user-agent strings in plugin-related requests

Network Indicators:

  • Outbound connections to suspicious domains from your WordPress site
  • Unexpected redirects from ThirstyAffiliates pages

SIEM Query:

source="web_server" AND (uri_path="*thirstyaffiliates*" AND (http_method="POST" AND (request_body="*<script>*" OR request_body="*javascript:*")))

🔗 References

📤 Share & Export