GHSA-64rr-pp78-62ww is a high-severity (CVSS 8.7) Cross-site Scripting (XSS) vulnerability in nukeviet/nukeviet. No vendor fix is recorded yet; mitigation options are listed below.
NukeViet CMS: Stored Cross-Site Scripting (XSS) via insufficient server-side input sanitization in Request class
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-64rr-pp78-62ww.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-64rr-pp78-62ww by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
nukeviet/nukevietReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | nukeviet/nukeviet | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nukeviet/nukeviet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of nukeviet/nukeviet has shipped for GHSA-64rr-pp78-62ww yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-64rr-pp78-62ww in your dependencies?
Find it across Packagist, including transitive dependencies.