Pix Para Woocommerce Plugin up to 2.13.3 on WordPress Payment Gateway Configuration authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Pix Para Woocommerce Plugin up to 2.13.3 on WordPress. Affected by this issue is some unknown functionality of the component Payment Gateway Configuration Handler. This manipulation causes authorization. This vulnerability is registered as CVE-2025-15400. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Pix Para Woocommerce Plugin up to 2.13.3 on WordPress. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component Payment Gateway Configuration Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity, and availability. The summary by CVE is:
The Pix para Woocommerce WordPress plugin through 2.13.3 allows any authenticated user to trigger AJAX actions that reset payment gateway configuration options without capability or nonce checks. This permits any authenticated users, such as subscribers to clear API credentials and webhook status, causing persistent disruption of OpenPix payment functionality.
The weakness was published by Md. Moniruzzaman Prodhan. The advisory is shared at wpscan.com. This vulnerability is known as CVE-2025-15400 since 12/31/2025. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/12/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202602-2039). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 6.5
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/31/2025 CVE reserved02/11/2026 Advisory disclosed
02/11/2026 VulDB entry created
02/12/2026 VulDB entry last update
Sources
Advisory: wpscan.comResearcher: Md. Moniruzzaman Prodhan
Status: Not defined
CVE: CVE-2025-15400 (🔒)
GCVE (CVE): GCVE-0-2025-15400
GCVE (VulDB): GCVE-100-345445
CNNVD: CNNVD-202602-2039 - WordPress plugin Pix para Woocommerce 安全漏洞
Entry
Created: 02/11/2026 08:29Updated: 02/12/2026 15:48
Changes: 02/11/2026 08:29 (54), 02/12/2026 11:32 (11), 02/12/2026 15:48 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.