Skip to main content
CVE-2026-129185VulnerabilityPublished

The PayPlus Payment Gateway plugin for WordPress is vulnerable to authorization bypass in all versions up to, and

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-129185· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 20 Nov 2026, 11:23 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.14.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
payplusPayPlus Payment GatewayAffected
  • <=8.3.4
Fixed in–

AI-suggested

Users should monitor the vendor's advisory for updates. Until a fix is available, restrict user roles and capabilities to trusted users only, and consider disabling the PayPlus plugin if possible to prevent exploitation.

Description

The PayPlus Payment Gateway plugin for WordPress contains an authorization bypass vulnerability in all versions up to and including 8.3.4. This flaw allows authenticated users with subscriber-level access or higher to generate payment page links for arbitrary WooCommerce orders, modify order payment methods and related metadata, and trigger API calls to PayPlus using the store's credentials. The vulnerability arises because the plugin fails to properly verify user authorization on an AJAX path, and no nonce or special capabilities are required to exploit it.

References

Community reviews

Loading reviews…