CVE-2026-113813VulnerabilityPublished 28 Oct 2026

The PayPlug for WooCommerce (Official) WordPress plugin before 3.1.1 does not perform any capability or ownership

Source GCVE Database

Authoritative record:CVE-2026-113813· High

Not known to be exploited : upgrade to 3.1.1 soon.

Data as of 28 Oct 2026, 07:14 UTC

Severity

High

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

Patch: Available – fixed in 3.1.1

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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-pp3q-4jh2-gvr2

What to do

Upgrade PayPlug for WooCommerce (Official) (WordPress plugin) to 3.1.1.

Affected software

Product	Affected	Fixed in
PayPlug for WooCommerce (Official)	Affected >=2.8.0 <3.1.1	Fixed in 3.1.1

AI-suggested

Upgrade the PayPlug for WooCommerce plugin to version 3.1.1 or later, where proper capability and ownership checks are implemented to prevent unauthorized access to order-related AJAX actions. No other mitigation is indicated by the available data.

Description

The PayPlug for WooCommerce WordPress plugin versions before 3.1.1 lack proper capability or ownership checks on certain unauthenticated AJAX actions. This flaw allows unauthenticated attackers to modify, read, and permanently delete arbitrary WooCommerce orders by supplying order identifiers.

Impact

Unauthenticated attackers can access and alter WooCommerce order data, including reading sensitive order contents, modifying order details, and permanently deleting orders. This compromises the integrity and confidentiality of order information within affected WooCommerce installations using the vulnerable plugin versions.

Summary

The PayPlug for WooCommerce (Official) WordPress plugin prior to version 3.1.1 contains a vulnerability where unauthenticated AJAX actions do not verify user capabilities or ownership of the targeted WooCommerce orders. As a result, attackers can manipulate order data without authentication by providing arbitrary order identifiers, leading to unauthorized modification, disclosure, or deletion of order information.

References

Community reviews

Loading reviews…