CVE-2024-10309: The Tracking Code Manager WordPress plugin before 2.4.0 does not sanitise and escape some of its metabox setti

Q: How do I fix CVE-2024-10309?

tracking code manager: upgrade to 2.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-10309 being exploited?

CVE-2024-10309 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-10309 affect?

CVE-2024-10309 affects tracking code manager. Severity is medium (CVSS 5.9). The Tracking Code Manager WordPress plugin before 2.4.0 does not sanitise and escape some of its metabox settings when outputing them in the page, which could allow users with a role as low as Contributor to perform Cross-Site Scripting att

Q: How urgent is CVE-2024-10309?

Priority 30/100. Public exploit reference

Routine

MEDIUM 5.9UPGRADE

CVE-2024-10309 is a medium-severity flaw (CVSS 5.9) affecting tracking code manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Tracking Code Manager WordPress plugin before 2.4.0 does not sanitise and escape some of its metabox settings when outputing them in the page, which could allow users with a role as low as Contributor to perform Cross-Site Scripting attacks.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.3% (top 82%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-01-30
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: data443

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-01-30 06:15 UTCPublished CVE record published
2026-06-17 06:55 UTCUpdated Record last modified

data443 tracking code manager UPGRADE

Affected: < 2.4.0

Fixed in: 2.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy tracking-code-manager || rpm -q tracking-code-manager || tracking-code-manager --version

2. UPGRADE to 2.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade tracking-code-manager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade tracking-code-manager

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-10309?

tracking code manager: upgrade to 2.4.0. Exact commands for each OS are on this page.

Is CVE-2024-10309 being exploited?

CVE-2024-10309 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-10309 affect?

CVE-2024-10309 affects tracking code manager. Severity is medium (CVSS 5.9). The Tracking Code Manager WordPress plugin before 2.4.0 does not sanitise and escape some of its metabox settings when outputing them in the page, which could allow users with a role as low as Contributor to perform Cross-Site Scripting att

How urgent is CVE-2024-10309?

Priority 30/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-6335 MEDIUM 4.8 UPGRADE The Tracking Code Manager WordPress plugin before 2.3.0 does not sanitise and escape some of its settings, whi

References

← Back to latest CVEs