CVE-2026-119171VulnerabilityPublished 11 Nov 2026

The Advanced Product Fields (Product Addons) for WooCommerce WordPress plugin from 1.6.22 to 1.7.3 does not validate

Source GCVE Database

Compare

Authoritative record:CVE-2026-119171· Medium 5.3

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

Data as of 11 Nov 2026, 10:17 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 1.7.4

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 11 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 10 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-r9r2-c6x9-7wrp

What to do

Upgrade Advanced Product Fields (Product Addons) for WooCommerce (WordPress plugin) to 1.7.4.

Affected software

Product	Affected	Fixed in
Advanced Product Fields (Product Addons) for WooCommerce	Affected >=1.6.22 <1.7.4	Fixed in 1.7.4

AI-suggested

If you cannot patch yet, merchants should consider disabling the affected plugin versions or implementing custom validation to enforce required paid options.

Description

The Advanced Product Fields (Product Addons) for WooCommerce WordPress plugin versions 1.6.22 through 1.7.3 contains a vulnerability where required paid product options are not properly validated. This allows unauthenticated users to add products to the cart and complete orders without paying the surcharge for required options, paying only the base product price.

Impact

Unauthenticated attackers can exploit this vulnerability to bypass payment for required paid product options, resulting in financial loss to the merchant. The integrity of the order pricing is compromised, but confidentiality and availability are not affected.

Summary

The vulnerability in the Advanced Product Fields (Product Addons) for WooCommerce plugin affects versions from 1.6.22 to 1.7.3. The plugin fails to validate that a submitted value for a required paid product option matches one of the configured choices, only checking that the value is not empty. This flaw enables unauthenticated users to bypass surcharges for required options when adding products to the cart and completing orders, effectively paying less than intended.

References

Community reviews

Loading reviews…