Skip to main content

Advanced Shipment Tracking CVE-2026-120558

| EUVDEUVD-2026-115663 HIGH
SQL Injection (CWE-89)
2026-11-03 Wordfence GHSA-cm75-3jj2-f2gr
7.2
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Shop Manager-level account
  2. Delivery
    Send POST to shipment-trackings REST endpoint
  3. Exploit
    Inject SQL via tracking_provider parameter
  4. Execution
    Append query against get_provider_slug_from_name()
  5. Impact
    Extract sensitive database records

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated account with Shop Manager-level privileges or higher (per CVSS PR:H); the attacker then calls the plugin's REST route POST /wp-json/wc-ast/v3/orders/<order_id>/shipment-trackings and supplies a malicious tracking_provider parameter, which reaches the vulnerable WC_Advanced_Shipment_Tracking_Admin::get_provider_slug_from_name() query where the value is concatenated into the $wpdb->prepare() format string instead of being bound. Affects all versions up to and including 3.9. The primary limiting factor is the Shop Manager privilege requirement - anonymous or low-privileged users cannot reach this; no non-default configuration is stated as necessary.

Impact

This is a genuine but privilege-gated SQL injection (CWE-89). The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N) and the description agree internally: exploitation is network-reachable over the REST API with low complexity and no user interaction, but requires PR:H - explicitly Shop Manager-level access or above. That high-privilege precondition is the dominant risk-limiter, since Shop Managers are trusted store operators, not anonymous internet users, so this is primarily an insider/compromised-account or privilege-boundary concern rather than a mass-exploitable perimeter flaw. No EPSS score, KEV listing, or exploit/PoC reference is present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The vuln.today priority is 'this_week' (not act_now/emergency), consistent with a serious-but-not-emergency issue. Net: patch within the normal cycle (this week) - it is a legitimate priority because the root cause (direct concatenation into the $wpdb->prepare() format string) gives a trusted-but-not-admin role full read access to the WordPress database, but the PR:H barrier keeps real-world blast radius well below that of an unauthenticated SQLi.

Exploit ScenarioDerived

An attacker who already holds (or has phished/compromised) a Shop Manager account sends a crafted POST request to /wp-json/wc-ast/v3/orders/<order_id>/shipment-trackings with a malicious tracking_provider value, which is concatenated into an unsafe SQL query and lets them append queries that read arbitrary data (e.g., user records, password hashes, secrets) from the WordPress database. The attack is low-complexity and needs no user interaction, but is bounded by the requirement for Shop Manager privileges. No public exploit code is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 03, 2026

SQL injection in the Advanced Shipment Tracking for WooCommerce plugin (all versions up to and including 3.9) allows an authenticated user with Shop Manager-level access or higher to inject SQL through the tracking_provider parameter of the POST /wp-json/wc-ast/v3/orders/<order_id>/shipment-trackings REST route, letting them append additional queries to an existing statement and read data from the WordPress database. The assessed impact is confidentiality-only (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N); integrity and availability effects are not established by the available evidence, and the practical barrier is the Shop Manager privilege requirement rather than any exotic configuration. No public exploit code has been identified at time of analysis, and there is no KEV or other active-exploitation signal in the supplied intelligence.

RemediationAI

Upgrade the Advanced Shipment Tracking for WooCommerce plugin to version 3.9.1, the release in which the vulnerable query construction and the corresponding REST controller code were reworked, as shown in the 3.9.1 source tags and the Trac changeset comparison referenced in the advisory (https://plugins.trac.wordpress.org/changeset?reponame=&new=3495394%40woo-advanced-shipment-tracking%2Ftrunk&old=3457814%40woo-advanced-shipment-tracking%2Ftrunk). No alternative mitigation is stated in the supplied sources, so the vendor update is the complete fix. Because the flaw requires Shop Manager-level access or higher, reducing the population of accounts holding Shop Manager or Administrator roles on affected sites limits exposure until the upgrade is applied, at the cost of restricting day-to-day order and shipment workflows for staff who currently rely on those roles. Reviewing existing users for unnecessary elevated roles, and auditing database or order-export activity from Shop Manager accounts on versions at or below 3.9, are the available detective steps while remediation is pending. Consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/76fb0ffd-32c1-483d-ae95-9bc70ba1c064?source=cve) for the vendor's own remediation wording.

Affected VersionsENISA

Advanced Shipment Tracking for WooCommerce 0 ≤3.9

Affected Packages

euvd advanced_shipment_tracking_for_woocommerce no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The target is a WordPress plugin (CPE vendor: zorem, product: advanced_shipment_tracking_for_woocommerce) that extends WooCommerce with shipment tracking records and exposes a custom REST namespace, wc-ast/v3, registered through the WordPress REST API. The root cause is CWE-89: in WC_Advanced_Shipment_Tracking_Admin::get_provider_slug_from_name(), the user-supplied tracking_provider value is concatenated directly into the format string passed to $wpdb->prepare() instead of being supplied as a bound placeholder argument. Because $wpdb->prepare() only parameterises the values substituted for its placeholders, text merged into the format string itself is emitted into the final SQL verbatim, so the parameterised-query protection is bypassed and attacker-controlled SQL fragments reach the database. The referenced 3.9.1 source files show both the admin class method and the REST controller being touched, indicating the fix reworked how the parameter is passed into the query and how the endpoint handles the request; the exact trigger path beyond reaching that method through the REST route is described in the supplied sources, but no exploit mechanics (payload, error-based versus blind extraction) are documented.

Know when Advanced Shipment Tracking For Woocommerce gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY HIGH
NVD 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 4.9 MEDIUM

Network REST endpoint with low complexity and no interaction, but Shop Manager access gives PR:H; description confirms only data extraction, so C:H with I:N/A:N.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionNVD

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.

Executive ViewAI

Why It Matters

A SQL injection vulnerability in the Advanced Shipment Tracking for WooCommerce plugin (versions up to 3.9) enables users with Shop Manager privileges or higher to read sensitive data from the WordPress database. This represents a medium-level risk because it requires an authenticated insider with elevated access, limiting the attack surface to trusted personnel or compromised accounts, but potential exposure of customer and order data warrants management attention.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis; restrict Shop Manager access to trusted users, deploy WAF with SQL injection rules, monitor database queries for anomalies, and consider disabling the vulnerable REST endpoint if not in use.

Threat Intelligence Overview

EPSS Score
0.3%
Top 72% exploitable
Prevalence
Medium
popular WooCommerce shipment-tracking plugin, common but not universal
Social Media
1
Sightings
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy