HomeWordPress vulnerabilitiesWPCargo Track & Trace
WPCargo Track & Trace vulnerabilities
WPCargo Track & Trace has 4 known vulnerabilities in this database. The most recent published record is dated 6 Aug 2026.
- Known vulnerabilities
- 4
- Active installs
- 10,000+
- Latest version
- 8.0.5
- Last updated
- 31 Jul 2026
- Most recent
- 6 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-12713 | Critical 9.1 | Before 8.0.4 | Fixed in 8.0.4 | 6 Aug 2026 |
| Cross-site scripting (XSS) CVE-2022-1435 | Medium 4.8 | Before 6.9.5 | Fixed in 6.9.5 | 16 May 2022 |
| Cross-site scripting (XSS) CVE-2022-1436 | Medium 6.1 | Before 6.9.5 | Fixed in 6.9.5 | 16 May 2022 |
| Remote code execution CVE-2021-25003 | Critical 9.8 | Before 6.9.0 | Fixed in 6.9.0 | 14 Mar 2022 |
Read the published descriptions
- CVE-2026-12713, 6 Aug 2026
- The WPCargo Track & Trace WordPress plugin before 8.0.4 does not properly sanitise and escape a parameter before using it in a SQL statement, allowing unauthenticated users to perform SQL injection attacks. This affects a code path distinct from the one addressed by CVE-2024-44004. CVE record
- CVE-2022-1435, 16 May 2022
- The WPCargo Track & Trace WordPress plugin before 6.9.5 does not sanitize and escapes some of its settings, which could allow high privilege users such as admin to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed. CVE record
- CVE-2022-1436, 16 May 2022
- The WPCargo Track & Trace WordPress plugin before 6.9.5 does not sanitise and escape the wpcargo_tracking_number parameter before outputting it back in the page, which could allow attackers to perform reflected Cross-Site Scripting attacks. CVE record
- CVE-2021-25003, 14 Mar 2022
- The WPCargo Track & Trace WordPress plugin before 6.9.0 contains a file which could allow unauthenticated attackers to write a PHP file anywhere on the web server, leading to RCE CVE record
What to do if you run WPCargo Track & Trace
If you run WPCargo Track & Trace, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WPCargo Track & Trace vulnerabilities
Free. We email you when a new vulnerability is published for WPCargo Track & Trace, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.