Quick Paypal Payments Plugin up to 5.7.50 on WordPress PayPal IPN data authenticity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 1.72 |
Summary
A vulnerability identified as problematic has been detected in Quick Paypal Payments Plugin up to 5.7.50. This vulnerability affects unknown code of the component PayPal IPN Handler. The manipulation leads to data authenticity. This vulnerability is referenced as CVE-2026-17008. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Quick Paypal Payments Plugin up to 5.7.50 and classified as problematic. This issue affects some unknown functionality of the component PayPal IPN Handler. The manipulation with an unknown input leads to a data authenticity vulnerability. Using CWE to declare the problem leads to CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. Impacted is integrity. The summary by CVE is:
The Quick Paypal Payments WordPress plugin through 5.7.50 does not verify the paid amount, receiver, or payment status in its PayPal IPN handler and marks an order paid on an order-token match alone, so a buyer who pays an arbitrary small amount can have a full-price order marked paid.
The advisory is shared at wpscan.com. The identification of this vulnerability is CVE-2026-17008 since 07/24/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. 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 08/12/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 5.7.0
- 5.7.1
- 5.7.2
- 5.7.3
- 5.7.4
- 5.7.5
- 5.7.6
- 5.7.7
- 5.7.8
- 5.7.9
- 5.7.10
- 5.7.11
- 5.7.12
- 5.7.13
- 5.7.14
- 5.7.15
- 5.7.16
- 5.7.17
- 5.7.18
- 5.7.19
- 5.7.20
- 5.7.21
- 5.7.22
- 5.7.23
- 5.7.24
- 5.7.25
- 5.7.26
- 5.7.27
- 5.7.28
- 5.7.29
- 5.7.30
- 5.7.31
- 5.7.32
- 5.7.33
- 5.7.34
- 5.7.35
- 5.7.36
- 5.7.37
- 5.7.38
- 5.7.39
- 5.7.40
- 5.7.41
- 5.7.42
- 5.7.43
- 5.7.44
- 5.7.45
- 5.7.46
- 5.7.47
- 5.7.48
- 5.7.49
- 5.7.50
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Data authenticityCWE: CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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
07/24/2026 CVE reserved08/12/2026 Advisory disclosed
08/12/2026 VulDB entry created
08/12/2026 VulDB entry last update
Sources
Advisory: wpscan.comStatus: Confirmed
CVE: CVE-2026-17008 (🔒)
GCVE (CVE): GCVE-0-2026-17008
GCVE (VulDB): GCVE-100-388985
Entry
Created: 08/12/2026 13:42Changes: 08/12/2026 13:42 (53)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.