CVE-2024-24878: WordPress Portugal CTT Tracking for WooCommerce plugin <= 2.1 - Reflected Cross Site Scripting (XSS) vulnerability
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Marco Almeida | Webdados Portugal CTT Tracking for WooCommerce portugal-ctt-tracking-woocommerce.This issue affects Portugal CTT Tracking for WooCommerce: from n/a through <= 2.1.
Security readout for executives and security teams
Plain-English summary
This is a reflected cross-site scripting flaw in a WordPress WooCommerce shipping-tracking plugin. If a vulnerable site uses the plugin and a user is induced to open attacker-controlled content, script could run in that user's browser. Business risk is highest for stores where admin or customer sessions could be exposed.
Executive priority
Prioritize remediation for customer-facing WooCommerce stores and sites used by administrators. Treat this as a high-risk plugin issue, but do not assume active compromise from the provided evidence alone.
Technical view
CVE-2024-24878 is CWE-79 in Portugal CTT Tracking for WooCommerce through version 2.1. The CVSS 3.1 score is 7.1: network reachable, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to WordPress/WooCommerce sites running Portugal CTT Tracking for WooCommerce version 2.1 or earlier. The source bundle does not identify affected routes, parameters, install counts, or a fixed version, so asset validation is required.
Exploitation context
The CVE record is not listed as CISA KEV in the bundle, and no cited source here confirms active exploitation. Risk remains meaningful because the CVSS vector indicates unauthenticated, network-reachable exploitation with low attack complexity, but it requires user interaction.
Researcher notes
The available bundle identifies reflected XSS, affected product, affected range through 2.1, CVSS vector, CWE-79, and Patchstack references. It does not provide vulnerable parameter details, proof of exploitation, exploit code, or a named patched version.
Mitigation direction
Inventory WordPress sites for the vulnerable plugin and version.
Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
Update the plugin if an official fixed version is available.
Disable or remove the plugin where it is unnecessary or unsupported.
Review WAF rules only as compensating control, not as the primary fix.
Validation and detection
Confirm whether the plugin is installed on each WooCommerce site.
Record the installed plugin version and compare it to <= 2.1.
Check vendor or Patchstack advisories for remediation status.
Review web logs for unusual requests to plugin-related pages.
Verify administrative users have not followed suspicious plugin-related links.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.