---
title: "CWE-85: Doubled Character XSS Manipulations"
url: https://radicalnotion.ai/cwe/cwe-85
type: cwe
description: "The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-85: Doubled Character XSS Manipulations

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

## Description

The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters.

## Modes of introduction

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

## 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 | - |

## Potential mitigations

### Implementation

Resolve all filtered input to absolute or canonical representations before processing.

### 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 tag attributes, 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

## Observed examples

| CVE | Description |
| --- | --- |
| CVE-2002-2086 | XSS using "\<script". |
| CVE-2000-0116 | Encoded "javascript" in IMG tag. |
| CVE-2001-1157 | Extra "\<" in front of SCRIPT tag. |

## Real CVEs with this weakness

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2024-13721 | Plethora Plugins Tabs + Accordions \<= 1.1.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via anchor | medium | 6.4 | - | No | 2025-01-25 |
| CVE-2022-41676 | TEAM JOHNLONG SOFTWARE CO., LTD. MAILD Mail Server - Cross-Site Scripting | medium | 5.4 | - | No | 2022-11-29 |

## Related attack patterns (CAPEC)

- [CAPEC-245](https://radicalnotion.ai/capec/capec-245): XSS Using Doubled Characters

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-79](https://radicalnotion.ai/cwe/cwe-79) | Improper Neutralization of Input During Web Page Generation |
| Peer | [CWE-675](https://radicalnotion.ai/cwe/cwe-675) | Multiple Operations on Resource in Single-Operation Context |

## Taxonomy mappings

| Taxonomy | Entry | Id | Fit |
| --- | --- | --- | --- |
| PLOVER | DOUBLE - Doubled character XSS manipulations, e.g. "\<script" | - | - |
| Software Fault Patterns | Tainted input to command | SFP24 | - |

## Frequently asked questions

### What is CWE-85?

The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters.

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

2 recorded CVEs are attributed to CWE-85, including CVE-2024-13721 and CVE-2022-41676.

### How do you prevent CWE-85?

Resolve all filtered input to absolute or canonical representations before processing.

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

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

### Is CWE-85 actively exploited?

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

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

---

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