CWE-173: Improper Handling of Alternate Encoding | Codefreex Skip to content

Security weakness

CWE-173 Improper Handling of Alternate Encoding

A variant-level weakness that can lead to accounts and admin areas exposed. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-173?

Improper Handling of Alternate Encoding: The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.

Business impact

What CWE-173 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Access Control

Accounts and admin areas exposed

Logins and permission checks can be bypassed, putting admin and customer accounts at risk.

  • Bypass Protection Mechanism

Free security check

Is CWE-173 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-173

Improper Handling of Alternate Encoding

The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.

Weakness ID
CWE-173
Type
Variant
Status
Draft
Introduced during
Implementation

Prevention

How to fix CWE-173, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
  2. 02

    Implementation

    • Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of.
    • 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.
    • Inputs should be decoded and canonicalized to the application’s current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.

How we fix it

From finding to fixed: how Codefreex closes CWE-173

  1. 01

    Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. 02

    Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. 03

    Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. 04

    Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-173: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-173?

CWE-173, “Improper Handling of Alternate Encoding”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.

How serious is CWE-173?

It can affect access control, with impacts such as bypass protection mechanism. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-173?

Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names. Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not.

Can Codefreex check my site for CWE-173?

Yes. A senior engineer reviews your site, store or app for CWE-173 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-173 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.