NukeViet: stored XSS through comment reply display names
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| nukeviet | nukeviet | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Nukeviet | Nukeviet |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w2w5-w2pw-r929 | NukeViet: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.533% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nukeviet
Nukeviet nukeviet |
|
| Vendors & Products |
Nukeviet
Nukeviet nukeviet |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | NukeViet CMS is a multi Content Management System. From the 4.x release line until 4.5.09, a low-privileged authenticated user can store script-breaking content in the first_name and last_name profile fields used to form a comment display name. Both reply links in themes/default/modules/comment/comment.tpl interpolate {COMMENT.post_name} into the inline onclick call to nv_commment_feedback(). HTML numeric references produced by Request::_get_title() are decoded by the browser before JavaScript parsing, so clicking Reply can terminate the string and execute attacker-controlled JavaScript in the visitor's origin, including an administrator's session. This issue is fixed in version 4.5.09. | |
| Title | NukeViet: stored XSS through comment reply display names | |
| Weaknesses | CWE-79 | |
| References |
| |
| Metrics |
cvssV3_1
|