DjangoBlog commit d186b1c through 6134ed6 Stored XSS via Comment Reactions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| liangliangyy | DjangoBlog | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Liangliangyy | Djangoblog |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.276% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Liangliangyy
Liangliangyy djangoblog |
|
| Vendors & Products |
Liangliangyy
Liangliangyy djangoblog |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | DjangoBlog commit d186b1c through commit 6134ed6 contains a stored cross-site scripting vulnerability that allows authenticated OAuth users to inject script via an unescaped nickname in comment reactions. Attackers can set their OAuth display name to a payload closing the single-quoted data-reactions attribute, then react to a comment to execute script in article visitors' browsers. | |
| Title | DjangoBlog commit d186b1c through 6134ed6 Stored XSS via Comment Reactions | |
| Weaknesses | CWE-79 | |
| References |
|
|
| Metrics |
cvssV3_1
|