CVE-2026-129185 in Payment Gateway Plugininfo

Summary

by MITRE • 11/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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The PayPlus Payment Gateway plugin for WordPress contains a critical authentication bypass vulnerability affecting all versions up to 8.3.4. This flaw stems from an improper verification of user authorization within the plugin's administrative functions, specifically on the AJAX request path. The core technical issue is caused by an inverted isset() predicate that renders the intended authorization block unreachable during execution. Consequently, any authenticated WordPress user with subscriber-level access or higher can bypass security checks without requiring a valid nonce or possessing special capabilities beyond basic login status. This architectural failure allows attackers to manipulate payment processing workflows and interact directly with external financial APIs using the store's credentials.

From an operational perspective, this vulnerability enables significant malicious actions against e-commerce stores running WooCommerce. An attacker can generate PayPlus payment page links for arbitrary orders belonging to any customer in the system. Furthermore, they possess the ability to overwrite the payment method associated with these orders and modify PayPlus-specific order metadata. This level of control over transaction data compromises the integrity of financial records and disrupts normal business operations by allowing unauthorized modifications to how payments are processed and recorded within the platform's database structure.

The severity of this vulnerability is amplified when a Point-of-Sale EMV device is configured for the store. In such environments, an attacker can trigger PayPlus API calls that initiate charge requests directly to the physical POS terminal using the merchant's credentials. This capability transforms a digital web application flaw into a potential threat against physical payment infrastructure, allowing unauthorized financial transactions to be processed through hardware terminals intended for legitimate customer interactions. The ability to force charges on external devices represents a severe risk to both merchant funds and consumer trust in the payment ecosystem.

This vulnerability aligns with CWE-285, which describes Improper Authorization, as the system fails to enforce proper access controls before allowing users to perform administrative actions. Additionally, it relates to CWE-347, specifically regarding improper verification of an authorization mechanism on a client-side or AJAX path where server-side checks are bypassed due to logic errors. In terms of offensive security frameworks, this behavior mirrors techniques found in the MITRE ATT&CK inventory under privilege escalation and unauthorized access patterns, particularly those involving API manipulation and credential abuse within web application contexts.

To mitigate this risk, administrators must immediately update the PayPlus Payment Gateway plugin to version 8.3.5 or later, where the authorization logic has been corrected to properly validate user permissions on all execution paths. Until an update is applied, site owners should consider restricting access to WordPress admin areas and AJAX endpoints to users with administrator-level privileges only, thereby limiting exposure to lower-privilege accounts such as subscribers or authors. Implementing strict input validation and ensuring that nonce verification is consistently applied across all sensitive operations can also help reduce the attack surface associated with similar logic flaws in other plugins. Regular security audits of payment gateway integrations are recommended to identify and remediate authorization bypasses before they can be exploited for financial fraud.

Responsible

Wordfence

Reservation

11/13/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00522

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!