CVE-2026-121633VulnerabilityPublished 6 Nov 2026

The Order Tracking WordPress plugin before 3.6.0 does not verify that a PayPal payment notification was sent to the

Source GCVE Database

Compare

Authoritative record:CVE-2026-121633· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.6.0 when convenient.

Data as of 6 Nov 2026, 10:35 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (WPScan)	CVSS 3.1	5.3

Patch: Available – fixed in 3.6.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 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 5 Nov 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-9jq5-vqj9-9f7c

What to do

Upgrade Order Tracking (WordPress plugin) to 3.6.0.

Affected software

Product	Affected	Fixed in
Order Tracking	Affected <3.6.0	Fixed in 3.6.0

AI-suggested

A fixed version 3.6.0 or later of the Order Tracking WordPress plugin should be applied to address this issue. Until then, merchants should be cautious about trusting payment status updates from the plugin without additional manual verification.

Description

The Order Tracking WordPress plugin versions before 3.6.0 have a vulnerability where the plugin does not verify that a PayPal payment notification was actually sent to the merchant's account or that the payment amount matches the order total before marking an order as paid. This flaw allows unauthenticated attackers to mark arbitrary orders as paid by making a trivial payment to their own PayPal account.

Impact

An attacker can exploit this vulnerability to fraudulently mark orders as paid without actually completing valid payments to the merchant. This can lead to financial losses for merchants due to unauthorized order fulfillment based on invalid payment confirmations. The integrity of the order payment process is compromised, but there is no direct confidentiality or availability impact reported.

References

Community reviews

Loading reviews…