NukeViet CMS: Unauthenticated Stored XSS in the Contact module via HTML sanitizer bypass
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 |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
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. Prior to 4.6.01, an unauthenticated visitor can submit Contact module content containing numeric HTML entities with more than eight leading zeros in a URL-bearing attribute. NukeViet\Core\Request::unhtmlentities() does not decode that form before filterAttr() checks for a javascript: scheme, but browsers decode it when rendering the stored content. With an allowed tag such as the default iframe, the reconstructed script URL executes in the administration origin when staff view the message, permitting session-riding actions while remaining unable to read the HttpOnly session cookie directly. This issue is fixed in version 4.6.01. | |
| Title | NukeViet CMS: Unauthenticated Stored XSS in the Contact module via HTML sanitizer bypass | |
| Weaknesses | CWE-172 CWE-184 CWE-79 |
|
| References |
| |
| Metrics |
cvssV3_1
|