GTPayment Donations <= 1.0.0 - Stored XSS via CSRF
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 | GTPayment Donations | affected |
|
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.184% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Harryhe
Harryhe gtpayment Donations |
|
| Weaknesses | CWE-352 | |
| CPEs | cpe:2.3:a:harryhe:gtpayment_donations:*:*:*:*:*:wordpress:*:* | |
| Vendors & Products |
Harryhe
Harryhe gtpayment Donations |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The GTPayment Donations WordPress plugin through 1.0.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack. | |
| Title | GTPayment Donations <= 1.0.0 - Stored XSS via CSRF | |
| References |
|