CVE-2026-41147

{"id": "CVE-2026-41147", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-41147", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-05-26T16:12:27.473907Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 8.7, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.8, "exploitabilityScore": 2.3}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "nukeviet", "product": "nukeviet", "versions": [{"status": "affected", "version": "< 4.5.08"}]}]}], "published": "2026-05-22T22:16:56.233", "references": [{"url": "https://github.com/nukeviet/nukeviet/commit/2a0860fbe22e2f6a3b90f802bf80b25e18699611", "source": "security-advisories@github.com"}, {"url": "https://github.com/nukeviet/nukeviet/releases/tag/4.5.08", "source": "security-advisories@github.com"}, {"url": "https://github.com/nukeviet/nukeviet/security/advisories/GHSA-64rr-pp78-62ww", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-79"}]}], "descriptions": [{"lang": "en", "value": "NukeViet CMS is a multi Content Management System. Versions 4.5.07 and prior contain 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). An attacker can inject malicious payloads which are stored server-side and executed in the browser of any user who views the content. Anyone viewing user-submitted content (such as administrators and moderators reviewing contact messages or comments) is impacted, and the vulnerability can be exploited by any anonymous visitor without authentication, with the Contact module used only as a proof of concept. Potential consequences include session hijacking through cookie theft, unauthorized actions performed under the victim's identity, defacement or redirection to phishing pages, and phishing attacks via manipulated email notifications. This issue has been fixed in version 4.5.08. If developers are unable to upgrade immediately, they should work around this issue by implementing server-side HTML sanitization in the Request class to strip or encode dangerous tags and attributes (e.g., <iframe>, srcdoc, event handlers like onerror/onload), enforcing a Content Security Policy (CSP) to restrict inline script execution, and set cookies with the HttpOnly flag to mitigate cookie theft via XSS."}, {"lang": "es", "value": "NukeViet CMS es un sistema de gesti\u00f3n de contenido m\u00faltiple. Las versiones 4.5.07 y anteriores contienen una vulnerabilidad de cross-site scripting (XSS) almacenado causada por una sanitizaci\u00f3n de entrada insuficiente del lado del server en la clase Request. La aplicaci\u00f3n se basa principalmente en el filtrado del lado del cliente para sanitizar etiquetas y atributos HTML en el contenido enviado por el usuario, lo cual puede ser eludido interceptando y modificando directamente las solicitudes HTTP (por ejemplo, usando Burp Suite). Un atacante puede inyectar cargas \u00fatiles maliciosas que se almacenan del lado del server y se ejecutan en el navegador de cualquier usuario que vea el contenido. Cualquiera que vea contenido enviado por el usuario (como administradores y moderadores que revisan mensajes de contacto o comentarios) se ve afectado, y la vulnerabilidad puede ser explotada por cualquier visitante an\u00f3nimo sin autenticaci\u00f3n, con el m\u00f3dulo de Contacto utilizado solo como una prueba de concepto. Las posibles consecuencias incluyen el secuestro de sesi\u00f3n a trav\u00e9s del robo de cookies, acciones no autorizadas realizadas bajo la identidad de la v\u00edctima, desfiguraci\u00f3n o redirecci\u00f3n a p\u00e1ginas de phishing, y ataques de phishing a trav\u00e9s de notificaciones de correo electr\u00f3nico manipuladas. Este problema ha sido solucionado en la versi\u00f3n 4.5.08. Si los desarrolladores no pueden actualizar de inmediato, deben solucionar este problema implementando la sanitizaci\u00f3n HTML del lado del server en la clase Request para eliminar o codificar etiquetas y atributos peligrosos (por ejemplo, <iframe>, srcdoc, manejadores de eventos como onerror/onload), aplicando una Pol\u00edtica de Seguridad de Contenido (CSP) para restringir la ejecuci\u00f3n de scripts en l\u00ednea, y configurar las cookies con la bandera HttpOnly para mitigar el robo de cookies a trav\u00e9s de XSS."}], "lastModified": "2026-07-23T11:10:00.120", "sourceIdentifier": "security-advisories@github.com"}