PeachPay Plugin up to 1.120.69 on WordPress information disclosure

Summaryinfo

A vulnerability was found in PeachPay Plugin up to 1.120.69. It has been rated as problematic. This affects an unknown function. This manipulation causes information disclosure. This vulnerability is handled as CVE-2026-103376. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as problematic was found in PeachPay Plugin up to 1.120.69. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

The PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI) WordPress plugin before 1.120.70 does not perform any capability or ownership check before returning an order's secret key in response to an unauthenticated request, allowing anyone to retrieve the key for any paid order and use it to view that order's customer name, email address, postal address and contents.

The advisory is shared at wpscan.com. This vulnerability is known as CVE-2026-103376 since 09/30/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 1.120.70 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-103255). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• PeachPay Plugin

Version

• 1.120.0
• 1.120.1
• 1.120.2
• 1.120.3
• 1.120.4
• 1.120.5
• 1.120.6
• 1.120.7
• 1.120.8
• 1.120.9
• 1.120.10
• 1.120.11
• 1.120.12
• 1.120.13
• 1.120.14
• 1.120.15
• 1.120.16
• 1.120.17
• 1.120.18
• 1.120.19
• 1.120.20
• 1.120.21
• 1.120.22
• 1.120.23
• 1.120.24
• 1.120.25
• 1.120.26
• 1.120.27
• 1.120.28
• 1.120.29
• 1.120.30
• 1.120.31
• 1.120.32
• 1.120.33
• 1.120.34
• 1.120.35
• 1.120.36
• 1.120.37
• 1.120.38
• 1.120.39
• 1.120.40
• 1.120.41
• 1.120.42
• 1.120.43
• 1.120.44
• 1.120.45
• 1.120.46
• 1.120.47
• 1.120.48
• 1.120.49
• 1.120.50
• 1.120.51
• 1.120.52
• 1.120.53
• 1.120.54
• 1.120.55
• 1.120.56
• 1.120.57
• 1.120.58
• 1.120.59
• 1.120.60
• 1.120.61
• 1.120.62
• 1.120.63
• 1.120.64
• 1.120.65
• 1.120.66
• 1.120.67
• 1.120.68
• 1.120.69

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion