CVE-2026-94599: NukeViet CMS: Reflected XSS in news module search via double URL decoding of the q parameter
NukeViet CMS is a multi Content Management System. From 4.5.00 until 4.5.13 and 4.6.02, an unauthenticated attacker can place a multiply encoded value in the news module search q parameter. $nvRequest->gettitle() decodes and sanitizes the input once, but modules/news/funcs/search.php subsequently applies urldecode() after sanitization. The resulting raw keyword reaches the {KEY} search-input attribute through searchtheme() and the no-results element through searchresulttheme() in the default and mobile themes, permitting attribute or tag injection and same-origin JavaScript execution when a victim opens the crafted search URL. This issue is fixed in versions 4.5.13 and 4.6.02.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.5.13 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.6.02
Event History
Frequently Asked Questions
Which deployments are affected by this issue?
NukeViet CMS versions from 4.5.00 through 4.5.13 and version 4.6.02 are identified as affected. The vulnerable rendering paths are present in the default and mobile themes.
Does exploitation require an account or special server-side access?
No. An unauthenticated attacker can craft a news-module search URL containing a multiply encoded q parameter, but a victim must open that URL for JavaScript to execute in the site's origin.
What makes the payload bypass input handling?
The q value is decoded and sanitized once by $nv_Request->get_title(), then modules/news/funcs/search.php applies urldecode() again. This second decode can turn the sanitized value into raw input that reaches HTML attribute and element output locations.
How can I determine whether a site is exposed?
Check the deployed NukeViet version and whether the news module search is available using the default or mobile theme. Systems running the listed affected releases should be treated as vulnerable until updated to a fixed release.
What should be done if an immediate update is not possible?
The provided data identifies the news search q parameter and the affected default and mobile themes, but does not specify a supported workaround. Restricting or disabling access to the news search function would reduce exposure until the vendor fix can be deployed.