CVE-2025-9463 MEDIUM

CVE-2025-9463: Payments Plugin and Checkout Plugin for WooCommerce: Stripe, PayPal, Square, Authorize.net <= 1.117.5 - Authenticated (Contributor+) SQL Injection via order_by Parameter

Vendor Peachpay
Product PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI)
Weakness CWE-89 · SQLi
Published September 10, 2025
Last update April 8, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The Payments Plugin and Checkout Plugin for WooCommerce: Stripe, PayPal, Square, Authorize.net plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order_by’ parameter in all versions up to, and including, 1.117.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Explanation of Vulnerability in Simple Terms

02Summary

PeachPay for WooCommerce versions up to 1.117.5 contain a SQL injection vulnerability in the payment processing logic. An authenticated user with low privileges can craft malicious input to read sensitive data from the site's database, including customer payment information and order details. The vulnerability requires valid user credentials but no additional user interaction.

What an attacker can do

03Attacker Capabilities

Read sensitive data from the site database, including customer records and payment information.

Potential impact on your site

04Site Impact

Customer payment data, order history, and other sensitive database records may be exposed to authenticated attackers.

Conditions required to exploit

05Prerequisites

Attacker must have a valid low-privilege user account (e.g., customer or subscriber role).

Key dates

06Disclosure timeline

September 10, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE