---
title: "CWE-81: Improper Neutralization of Script in an Error Message Web Page"
url: https://radicalnotion.ai/cwe/cwe-81
type: cwe
description: "The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters that could be interpreted as web-scripting elements when they are sent to an error page."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-81: Improper Neutralization of Script in an Error Message Web Page

- **Abstraction:** Variant
- **Structure:** Simple
- **Status:** Incomplete
- **CVEs with this as primary weakness:** 7
- **Of those, in CISA KEV:** 0
- **New in 2026:** 1
- **CWE catalog version:** 4.21

## Description

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters that could be interpreted as web-scripting elements when they are sent to an error page.

## Background

Error pages may include customized 403 Forbidden or 404 Not Found pages.

## Modes of introduction

| Phase | Note |
| --- | --- |
| Implementation | - |
| Operation | - |

## Applicable platforms

**Technologies:** Web Based (Undetermined), Web Server (Undetermined)

## Common consequences

| Scope | Impact | Note |
| --- | --- | --- |
| Confidentiality, Integrity, Availability | Read Application Data, Execute Unauthorized Code or Commands | When an attacker can trigger an error that contains script syntax within the attacker's input, then cross-site scripting attacks may be possible. |

## Potential mitigations

### Implementation

Do not write user-controlled input to error pages.

### 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 (Output Encoding)

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 (Attack Surface Reduction)

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.

Effectiveness: Defense in Depth

## Detection methods

### Automated Static Analysis

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.)

## Observed examples

| CVE | Description |
| --- | --- |
| CVE-2002-0840 | XSS in default error page from Host: header. |
| CVE-2002-1053 | XSS in error message. |
| CVE-2002-1700 | XSS in error page from targeted parameter. |

## Real CVEs with this weakness

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2022-4361 | Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC | critical | 10.0 | - | No | 2023-07-07 |
| CVE-2022-4137 | Keycloak: reflected xss attack | high | 8.1 | - | No | 2023-09-25 |
| CVE-2025-24344 | - | medium | 6.3 | - | No | 2025-04-30 |
| CVE-2026-41568 | Moby: Race condition in docker cp allows creation of arbitrary empty files on the host via symlink swap | medium | 6.1 | - | No | 2026-06-12 |
| CVE-2024-6892 | Journyx Reflected Cross Site Scripting | medium | 6.1 | - | No | 2024-08-07 |
| CVE-2019-25027 | Reflected cross-site scripting in default RouteNotFoundError view in Vaadin 10 and 11-13 | medium | 6.1 | - | No | 2021-04-23 |
| CVE-2025-0883 | vulnerability has been discovered in OpenText™ Service Manager. | low | 2.1 | - | No | 2025-03-12 |

## Related attack patterns (CAPEC)

- [CAPEC-198](https://radicalnotion.ai/capec/capec-198): XSS Targeting Error Pages

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-79](https://radicalnotion.ai/cwe/cwe-79) | Improper Neutralization of Input During Web Page Generation |
| Can also be | [CWE-209](https://radicalnotion.ai/cwe/cwe-209) | Generation of Error Message Containing Sensitive Information |
| Can also be | [CWE-390](https://radicalnotion.ai/cwe/cwe-390) | Detection of Error Condition Without Action |

## Taxonomy mappings

| Taxonomy | Entry | Id | Fit |
| --- | --- | --- | --- |
| PLOVER | XSS in error pages | - | - |
| Software Fault Patterns | Tainted input to command | SFP24 | - |

## Frequently asked questions

### What is CWE-81?

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters that could be interpreted as web-scripting elements when they are sent to an error page.

### What CVEs are caused by CWE-81?

7 recorded CVEs are attributed to CWE-81, including CVE-2022-4361, CVE-2022-4137 and CVE-2025-24344.

### How do you prevent CWE-81?

Do not write user-controlled input to error pages.

### How is CWE-81 detected?

Automated Static Analysis: 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.)

### What are the consequences of CWE-81?

Exploiting CWE-81 can lead to: Read Application Data, Execute Unauthorized Code or Commands.

### Is CWE-81 actively exploited?

7 recorded CVEs are caused by CWE-81; none are currently in CISA's KEV catalog of actively exploited flaws.

Primary source: [MITRE CWE](https://cwe.mitre.org/data/definitions/81.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/cwe/cwe-81). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
