CWE-84: Improper Neutralization of Encoded URI Schemes in a Web Page

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-84 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-84, Improper Neutralization of Encoded URI Schemes in a Web Page, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Apply Input Validation controls for Improper Neutralization of Encoded URI Schemes in a Web Page

MITRE associates mitigation with Implementation; the listed strategies include Input Validation, Output Encoding, and Attack Surface Reduction; recorded impacts include Unexpected State. Use these source-defined anchors to turn CWE-84 into implementation, review, and verification checks for the affected component.

CWE-84: Improper Neutralization of Encoded URI Schemes in a Web Page — MITRE CWE

Triage CWE-84 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-84, Improper Neutralization of Encoded URI Schemes in a Web Page, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-84

Apply MITRE's full root-cause mapping guidance when using CWE-84, Improper Neutralization of Encoded URI Schemes in a Web Page. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-84 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-84, Improper Neutralization of Encoded URI Schemes in a Web Page. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-84: Improper Neutralization of Encoded URI Schemes in a Web Page?+

CWE-84: Improper Neutralization of Encoded URI Schemes in a Web Page is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The web application improperly neutralizes user-controlled input for executable script disguised with URI encodings.

What are the security consequences of Improper Neutralization of Encoded URI Schemes in a Web Page?+

If exploited, CWE-84 (Improper Neutralization of Encoded URI Schemes in a Web Page) it can compromise Integrity, leading to outcomes such as Unexpected State.

How do you prevent or mitigate Improper Neutralization of Encoded URI Schemes in a Web Page?+

Recommended mitigations for CWE-84 include: Resolve all URIs to absolute or canonical representations before processing. 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.

Which programming languages are affected by Improper Neutralization of Encoded URI Schemes in a Web Page?+

CWE-84 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Neutralization of Encoded URI Schemes in a Web Page?+

MITRE documents real CVEs mapped to CWE-84, including CVE-2005-0563, CVE-2005-2276, CVE-2005-0692, CVE-2002-0117 and CVE-2002-0118. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-84 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-84: Improper Neutralization of Encoded URI Schemes in a Web Page

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Strategy

Phase

Description

Strategy

Detection Methods

Code Examples & CVEs

Observed CVE Examples (5)

CWE Relationships

Parent Weaknesses