Tracking Code Manager < 2.4.0 - Contributor+ Stored XSS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Unknown | Tracking Code Manager | unaffected |
|
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.273% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Data443
Data443 tracking Code Manager |
|
| Weaknesses | CWE-79 | |
| CPEs | cpe:2.3:a:data443:tracking_code_manager:*:*:*:*:*:wordpress:*:* | |
| Vendors & Products |
Data443
Data443 tracking Code Manager |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Tracking Code Manager < 2.4.0 - Contributor+ Stored XSS | |
| References |
|