# CVE-2026-120558: The Advanced Shipment Tracking for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the `tracking_provider` parameter of


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-cm75-3jj2-f2gr

## What is CVE-2026-120558?

CVE-2026-120558 is a high-severity vulnerability in zorem Advanced Shipment Tracking for WooCommerce, published on 3 Nov 2026. 

### Official description

The Advanced Shipment Tracking for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the `tracking_provider` parameter of the `POST /wp-json/wc-ast/v3/orders/<order_id>/shipment-trackings` REST endpoint in all versions up to, and including, 3.9. This is due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query in `WC_Advanced_Shipment_Tracking_Admin::get_provider_slug_from_name()` — the value is concatenated directly into the format string of `$wpdb->prepare()` rather than bound as a parameter, bypassing parameterised-query protections. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to append additional SQL queries into the already-existing query that can be used to extract sensitive information from the database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-120558?


## How do I fix CVE-2026-120558?

No fix has been published for CVE-2026-120558 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120558 being exploited?

There is no known exploitation of CVE-2026-120558 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120558 and fix it if it is affected.

What it is: CVE-2026-120558 is a high-severity vulnerability in zorem Advanced Shipment Tracking for WooCommerce, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120558 in the wild and no public exploit code.

Affected product: zorem Advanced Shipment Tracking for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120558/ (Markdown: https://insights.sbomify.com/CVE-2026-120558/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120558
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120558
- OSV: https://osv.dev/vulnerability/CVE-2026-120558

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120558/
Summaries are generated and may contain mistakes; the official description above is the record.
