Nexi XPay Build <= 7.6.2 - Unauthenticated Payment Bypass via NPG Notification Handler
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Unknown | Nexi XPay Build | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wordpress-extensions | Nexi Xpay Build |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.131% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress-extensions
Wordpress-extensions nexi Xpay Build |
|
| Vendors & Products |
Wordpress-extensions
Wordpress-extensions nexi Xpay Build |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-285 |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-345 | |
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-285 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Nexi XPay Build WordPress plugin through 7.6.2 does not correctly validate the security token on its payment notification route, accepting the request when the target order has no stored token, which allows unauthenticated attackers to mark arbitrary orders as paid, or to mark genuinely paid orders as failed. | |
| Title | Nexi XPay Build <= 7.6.2 - Unauthenticated Payment Bypass via NPG Notification Handler | |
| References |
| |
| Metrics |
cvssV3_1
|