CWE-80 Variante Incompleto High likelihood

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

This vulnerability, commonly known as Basic Cross-Site Scripting (XSS), occurs when a web application fails to properly sanitize user input containing HTML and JavaScript tags. When untrusted data…

Definición

What is CWE-80?

This vulnerability, commonly known as Basic Cross-Site Scripting (XSS), occurs when a web application fails to properly sanitize user input containing HTML and JavaScript tags. When untrusted data containing characters like <, >, and & is rendered directly into a webpage, a browser may execute it as active code, not just display it as text.
At its core, this flaw allows attackers to inject malicious scripts into web pages viewed by other users. These scripts execute within the victim's browser context, enabling actions like stealing session cookies, logging keystrokes, defacing websites, or redirecting users to malicious sites. The risk is highest in any part of an application that displays user-provided data without proper validation, such as comment sections, user profiles, or search result pages. Preventing Basic XSS requires a consistent strategy of output encoding or contextual escaping. Instead of trying to filter out 'bad' input, you should proactively encode all user-controlled data before inserting it into HTML. This means converting special characters into their safe HTML entity equivalents (e.g., < for <). Rely on well-tested libraries for your framework to perform this encoding, and never use insecure methods like `innerHTML` or `document.write()` with raw user input.
Vulnerability Diagram CWE-80
Reflected XSS (Basic) Crafted URL ?q=<script>…</script> Server echoes q into HTML <p>You searched: q</p> no encoding Victim browser runs reflected script Session cookies leak The malicious URL is shared (email/chat); reply page reflects the script.
Impacto en el mundo real

Real-world CVEs caused by CWE-80

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    Identifica una ruta de código que maneje entrada no confiable sin validación.

  2. 2

    Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.

  3. 3

    Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.

  4. 4

    Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.

Ejemplo de código vulnerable

Vulnerable JSP

In the following example, a guestbook comment isn't properly encoded, filtered, or otherwise neutralized for script-related tags before being displayed in a client browser.

Vulnerable JSP 
<% for (Iterator i = guestbook.iterator(); i.hasNext(); ) {
  	Entry e = (Entry) i.next(); %>
  	<p>Entry #<%= e.getId() %></p>
  	<p><%= e.getText() %></p>
  	<%
  	} %>
Ejemplo de código seguro

Secure pseudo

Seguro pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención

How to prevent CWE-80

  • Implementation Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.
  • Implementation Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component. The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.
  • Implementation With Struts, write all data from form beans with the bean's filter attribute set to true.
  • Implementation To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XMLHTTPRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.
Señales de detección

How to detect CWE-80

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-80 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-80?

This vulnerability, commonly known as Basic Cross-Site Scripting (XSS), occurs when a web application fails to properly sanitize user input containing HTML and JavaScript tags. When untrusted data containing characters like , and & is rendered directly into a webpage, a browser may execute it as active code, not just display it as text.

¿Qué gravedad tiene CWE-80?

MITRE califica la probabilidad de explotación como Alta — esta debilidad se explota activamente en la práctica y debe priorizarse para su remediación.

¿Qué lenguajes o plataformas se ven afectados por CWE-80?

MITRE no ha especificado plataformas afectadas para esta CWE — puede aplicar a la mayoría de los stacks de aplicaciones.

¿Cómo puedo prevenir CWE-80?

Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data…

¿Cómo detecta y corrige Plexicus CWE-80?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-80 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.

¿Dónde puedo aprender más sobre CWE-80?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/80.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-80

CWE-79 Padre

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

This vulnerability occurs when a web application fails to properly sanitize or encode user-supplied input before displaying it on a…

CWE-81 Hermano

Improper Neutralization of Script in an Error Message Web Page

This vulnerability occurs when an application fails to properly sanitize user-supplied input before displaying it within an error message…

CWE-83 Hermano

Improper Neutralization of Script in Attributes in a Web Page

This vulnerability occurs when a web application fails to properly sanitize or block JavaScript URIs (like 'javascript:') within HTML tag…

CWE-84 Hermano

Improper Neutralization of Encoded URI Schemes in a Web Page

This vulnerability occurs when a web application fails to properly sanitize user-supplied input that contains malicious scripts disguised…

CWE-85 Hermano

Doubled Character XSS Manipulations

This vulnerability occurs when a web application fails to properly sanitize user input that contains doubled characters, allowing…

CWE-86 Hermano

Improper Neutralization of Invalid Characters in Identifiers in Web Pages

This vulnerability occurs when an application fails to properly filter or escape invalid characters within web identifiers like HTML tag…

CWE-87 Hermano

Improper Neutralization of Alternate XSS Syntax

This vulnerability occurs when an application fails to properly sanitize user-supplied input that uses alternative methods to execute…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo