CVE-2026-41147

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 as onerror, onload).
• Apply a Content Security Policy (CSP) header to restrict inline script execution.
• Ensure cookies are set with the HttpOnly flag 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

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="&lt;img src=1 onerror=alert(document.cookie)&gt;"></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

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-41147 has a CVSS score of 8.7 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

This vulnerability has been fixed in NukeViet 4.5.08. Users should upgrade to version >= 4.5.08.

1. What is CVE-2026-41147? CVE-2026-41147 is a high-severity cross-site scripting (XSS) vulnerability in nukeviet/nukeviet (composer), affecting versions <= 4.4.01. No fixed version is listed yet. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-41147? CVE-2026-41147 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of nukeviet/nukeviet are affected by CVE-2026-41147? nukeviet/nukeviet (composer) versions <= 4.4.01 is affected.
4. Is there a fix for CVE-2026-41147? No fixed version is listed for CVE-2026-41147 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-41147 exploitable, and should I be worried? Whether CVE-2026-41147 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41147 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41147? No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.