Music Request Manager <= 1.3 - 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 | Music Request Manager | 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.187% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-352 | |
| CPEs | cpe:2.3:a:scriptonite:music_request_manager:*:*:*:*:*:wordpress:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Scriptonite
Scriptonite music Request Manager |
|
| CPEs | cpe:2.3:a:scriptonite:music_request_manager:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Scriptonite
Scriptonite music Request Manager |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Music Request Manager WordPress plugin through 1.3 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 | Music Request Manager <= 1.3 - Stored XSS via CSRF | |
| References |
|