CVE-2025-14463 MEDIUM

CVE-2025-14463: Payment Button for PayPal <= 1.2.3.41 - Missing Authorization to Unauthenticated Arbitrary Order Creation

Vendor Naa986
Product Payment Button for PayPal
Weakness CWE-862 · Missing authorization
Published January 17, 2026
Last update April 8, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

The Payment Button for PayPal plugin for WordPress is vulnerable to unauthorized order creation in all versions up to, and including, 1.2.3.41. This is due to the plugin exposing a public AJAX endpoint (`wppaypalcheckout_ajax_process_order`) that processes checkout results without any authentication or server-side verification of the PayPal transaction. This makes it possible for unauthenticated attackers to create arbitrary orders on the site with any chosen transaction ID, payment status, product name, amount, or customer information via direct POST requests to the AJAX endpoint, granted they can bypass basic parameter validation. If email sending is enabled, the plugin will also trigger purchase receipt emails to any email address supplied in the request, leading to order database corruption and unauthorized outgoing emails without any real PayPal transaction taking place.

Explanation of Vulnerability in Simple Terms

02Summary

The Payment Button for PayPal plugin through version 1.2.3.41 lacks proper authorization checks, allowing unauthenticated attackers to modify payment button settings or data over the network. No user interaction is required. The vulnerability affects the integrity of payment configurations but does not expose sensitive data or cause service disruption.

What an attacker can do

03Attacker Capabilities

Modify payment button settings or transaction data without authentication.

Potential impact on your site

04Site Impact

Attackers can alter payment button configurations, potentially redirecting payments or changing transaction terms.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

January 17, 2026 CVE published
April 8, 2026 Record updated