GHSA-64RR-PP78-62WW
Vulnerability from github – Published: 2026-05-15 16:45 – Updated: 2026-06-08 23:20Impact
NukeViet CMS <= 4.5.08 contains a Stored Cross-Site Scripting (XSS) vulnerability caused by insufficient server-side input sanitization in the Request class. The application relies primarily on client-side filtering to sanitize HTML tags and attributes in user-submitted content, which can be bypassed by intercepting and modifying HTTP requests directly (e.g., using Burp Suite).
This affects any module or functionality that accepts user HTML input through the Request class. An attacker can inject malicious payloads such as <iframe srcdoc="<img src=1 onerror=alert(document.cookie)>"></iframe>, which are stored server-side and executed in the browser of any user who views the content.
Who is impacted: - Administrators and moderators who view user-submitted content (e.g., contact messages, comments, or any module using the Request class for HTML input). - The Contact module was used as a proof of concept, but the vulnerability is not limited to this module. - No authentication is required to exploit this vulnerability, making it accessible to any anonymous visitor.
Potential impact includes: - Session hijacking via cookie theft (for non-HttpOnly cookies) - Performing actions on the application under the victim's identity - Defacement or redirection to phishing pages - Phishing attacks via manipulated email notifications
Patches
This vulnerability has been fixed in NukeViet 4.5.08. Users should upgrade to version >= 4.5.08.
Workarounds
- Implement server-side HTML sanitization in the Request class to strip or encode dangerous tags and attributes (e.g.,
<iframe>,srcdoc, event handlers such asonerror,onload). - Apply a Content Security Policy (CSP) header to restrict inline script execution.
- Ensure cookies are set with the
HttpOnlyflag to mitigate cookie theft via XSS.
Resources
- Affected source: https://github.com/nukeviet/nukeviet/blob/nukeviet4.5/modules/contact/funcs/main.php
- CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'): https://cwe.mitre.org/data/definitions/79.html
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "nukeviet/nukeviet"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "4.4.01"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-41147"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-15T16:45:03Z",
"nvd_published_at": "2026-05-22T22:16:56Z",
"severity": "HIGH"
},
"details": "### Impact\n\nNukeViet CMS \u003c= 4.5.08 contains a Stored Cross-Site Scripting (XSS) vulnerability caused by insufficient server-side input sanitization in the Request class. The application relies primarily on client-side filtering to sanitize HTML tags and attributes in user-submitted content, which can be bypassed by intercepting and modifying HTTP requests directly (e.g., using Burp Suite).\n\nThis affects any module or functionality that accepts user HTML input through the Request class. An attacker can inject malicious payloads such as `\u003ciframe srcdoc=\"\u0026lt;img src=1 onerror=alert(document.cookie)\u0026gt;\"\u003e\u003c/iframe\u003e`, which are stored server-side and executed in the browser of any user who views the content.\n\n**Who is impacted:**\n- Administrators and moderators who view user-submitted content (e.g., contact messages, comments, or any module using the Request class for HTML input).\n- The Contact module was used as a proof of concept, but the vulnerability is not limited to this module.\n- No authentication is required to exploit this vulnerability, making it accessible to any anonymous visitor.\n\n**Potential impact includes:**\n- Session hijacking via cookie theft (for non-HttpOnly cookies)\n- Performing actions on the application under the victim\u0027s identity\n- Defacement or redirection to phishing pages\n- Phishing attacks via manipulated email notifications\n\n### Patches\n\nThis vulnerability has been fixed in NukeViet 4.5.08. Users should upgrade to version \u003e= 4.5.08.\n\n### Workarounds\n\n- Implement server-side HTML sanitization in the Request class to strip or encode dangerous tags and attributes (e.g., `\u003ciframe\u003e`, `srcdoc`, event handlers such as `onerror`, `onload`).\n- Apply a Content Security Policy (CSP) header to restrict inline script execution.\n- Ensure cookies are set with the `HttpOnly` flag to mitigate cookie theft via XSS.\n\n### Resources\n\n- Affected source: https://github.com/nukeviet/nukeviet/blob/nukeviet4.5/modules/contact/funcs/main.php\n- CWE-79: Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027): https://cwe.mitre.org/data/definitions/79.html",
"id": "GHSA-64rr-pp78-62ww",
"modified": "2026-06-08T23:20:55Z",
"published": "2026-05-15T16:45:03Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/nukeviet/nukeviet/security/advisories/GHSA-64rr-pp78-62ww"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41147"
},
{
"type": "WEB",
"url": "https://github.com/nukeviet/nukeviet/commit/2a0860fbe22e2f6a3b90f802bf80b25e18699611"
},
{
"type": "PACKAGE",
"url": "https://github.com/nukeviet/nukeviet"
},
{
"type": "WEB",
"url": "https://github.com/nukeviet/nukeviet/releases/tag/4.5.08"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "NukeViet CMS: Stored Cross-Site Scripting (XSS) via insufficient server-side input sanitization in Request class"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.