CWE-647: Use of Non-Canonical URL Paths for Authorization Skip to content

Security weakness

CWE-647 Use of Non-Canonical URL Paths for Authorization Decisions

A variant-level weakness that can lead to private data exposed and 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-647?

Use of Non-Canonical URL Paths for Authorization Decisions: The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical.

Business impact

What CWE-647 could cost your business

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

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • Read Files or Directories

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

Use of Non-Canonical URL Paths for Authorization Decisions

The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical.

If an application defines policy namespaces and makes authorization decisions based on the URL, but it does not require or convert to a canonical URL before making the authorization decision, then it opens the application to attack. For example, if the application only wants to allow access to http://www.example.com/mypage, then the attacker might be able to bypass this restriction using equivalent URLs such as:

http://WWW.EXAMPLE.COM/mypage

http://www.example.com/%6Dypage (alternate encoding)

http://192.168.1.1/mypage (IP address)

http://www.example.com/mypage/ (trailing /)

http://www.example.com:80/mypage

Weakness ID
CWE-647
Type
Variant
Status
Incomplete
Likelihood of exploit
High
Applies to
Web Server
Introduced during
Implementation, Operation

Prevention

How to fix CWE-647, phase by phase

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

  1. 01

    Architecture and Design

    • Make access control policy based on path information in canonical form, with all alternate encodings rejected (which can be accomplished by a default deny rule). Consider very restrictive regular expressions to validate that the path is in the expected form. Reject all alternate path encodings that are not in the expected canonical form.

Detection and evidence

How CWE-647 is found, and where it has hit

The testing methods MITRE recommends for finding it.

How it is detected

  • Automated Static AnalysisAutomated 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.

How we fix it

From finding to fixed: how Codefreex closes CWE-647

  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-647: FAQs

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

What is CWE-647?

CWE-647, “Use of Non-Canonical URL Paths for Authorization Decisions”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical.

How serious is CWE-647?

MITRE rates the likelihood of exploit as High. It can affect access control, confidentiality, with impacts such as bypass protection mechanism, read files or directories. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-647?

Make access control policy based on path information in canonical form, with all alternate encodings rejected (which can be accomplished by a default deny rule). Consider very restrictive regular expressions to validate that the path is in the expected form.

Can Codefreex check my site for CWE-647?

Yes. A senior engineer reviews your site, store or app for CWE-647 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.

Which technologies does CWE-647 affect?

MITRE lists it as applicable to Web Server. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-647 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.