CVE-2024-10309

5.9 MEDIUM

📋 TL;DR

This vulnerability in the Tracking Code Manager WordPress plugin allows users with Contributor-level permissions or higher to inject malicious scripts into metabox settings. When these settings are displayed on pages, the scripts execute in visitors' browsers, enabling cross-site scripting attacks. WordPress sites using vulnerable plugin versions are affected.

💻 Affected Systems

Products:
  • WordPress Tracking Code Manager plugin
Versions: All versions before 2.4.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with the vulnerable plugin and at least one user with Contributor role or higher.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker with contributor access could inject persistent XSS payloads that steal admin credentials, hijack user sessions, deface the website, or redirect visitors to malicious sites.

🟠

Likely Case

A malicious contributor injects tracking scripts, cookie stealers, or adware that affects all visitors viewing pages containing the compromised metabox settings.

🟢

If Mitigated

With proper role-based access controls and input validation, the attack surface is limited to trusted contributors only, reducing the risk of exploitation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires contributor-level access. The vulnerability is publicly documented with technical details available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.4.0

Vendor Advisory: https://wpscan.com/vulnerability/9eb21250-34bd-4600-a0a5-7c5117f69f04/

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Tracking Code Manager' and click 'Update Now'. 4. Verify the plugin version is 2.4.0 or higher.

🔧 Temporary Workarounds

Temporarily disable plugin

all

Deactivate the vulnerable plugin until patching is possible

wp plugin deactivate tracking-code-manager

Restrict user roles

all

Temporarily remove Contributor role permissions or elevate to higher trusted roles only

🧯 If You Can't Patch

  • Implement strict Content Security Policy (CSP) headers to mitigate XSS impact
  • Use web application firewall (WAF) rules to block suspicious script injection patterns

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins → Tracking Code Manager version number

Check Version:

wp plugin get tracking-code-manager --field=version

Verify Fix Applied:

Confirm plugin version is 2.4.0 or higher in WordPress admin plugins page

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to wp-admin/admin-ajax.php with metabox parameter modifications
  • Multiple failed login attempts followed by successful contributor login

Network Indicators:

  • Outbound connections to suspicious domains from your WordPress server
  • Unexpected JavaScript payloads in HTTP responses containing tracking-code-manager references

SIEM Query:

source="wordpress.log" AND ("tracking-code-manager" OR "metabox") AND ("script" OR "javascript" OR "onload" OR "onerror")

🔗 References

📤 Share & Export