Answer in brief
CVE-2026-129185 records a Medium severity (CVSS 4.3) vulnerability in PayPlus Payment Gateway <= 8.3.4 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Order Payment Manipulation via generate-link-payment AJAX Action. The current sources do not mark it as known exploited. The current feed maps payplus/PayPlus Payment Gateway (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps payplus/PayPlus Payment Gateway (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| payplus/PayPlus Payment Gatewaygeneric | >=0 <=8.3.4 | Not reported |
Published upstream
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 20, 2026
The PayPlus Payment Gateway plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 8.3.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to generate PayPlus payment page links for arbitrary WooCommerce orders belonging to any customer, overwrite those orders' payment method and PayPlus-related order meta, and trigger PayPlus API calls using the store's credentials — including, when a POS EMV device is configured, initiating a charge request to the store's physical POS terminal. The exploit requires no nonce and no special capability beyond being logged in, as the authorization block is unreachable on the AJAX path due to the inverted isset() predicate.
Quoted source text, attributed separately from HOL analysis.