CVE-2026-123124VulnerabilityPublished 13 Nov 2026

The WooCommerce Vindi Pagamento WordPress plugin through 0.8.3 does not perform any authorisation check when updating

Source GCVE Database

Compare

Authoritative record:CVE-2026-123124· High

Not known to be exploited.

Data as of 13 Nov 2026, 07:45 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-x5m4-f9xg-mvjw

What to do

Affected software

Product	Affected	Fixed in
WooCommerce Vindi Pagamento	Affected <=0.8.3	Fixed in–

AI-suggested

Until a fix is available, restrict access to the order edit pages to trusted users only and consider disabling legacy order storage if possible.

Description

The WooCommerce Vindi Pagamento WordPress plugin up to version 0.8.3 lacks authorization checks when updating an order's shipment tracking code and fails to escape this code when displayed on the order edit page. This allows unauthenticated attackers to inject stored cross-site scripting (XSS) payloads that execute when administrators or shop managers view affected orders. The vulnerability affects sites using WooCommerce's legacy order storage system.

Impact

Unauthenticated attackers can inject malicious scripts into the shipment tracking code field of orders, leading to stored cross-site scripting attacks. These scripts execute in the context of administrators and shop managers who view the affected order pages, potentially allowing session hijacking, privilege escalation, or other malicious actions within the administrative interface. The impact is limited to sites using WooCommerce's legacy order storage.

References

Community reviews

Loading reviews…