Security weakness
CWE-1007 Insufficient Visual Distinction of Homoglyphs Presented to User
A base-level weakness that can lead to private data exposed, data and pages or code changed. 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-1007?
Insufficient Visual Distinction of Homoglyphs Presented to User: The product displays information or identifiers to a user, but the display mechanism does not make it easy for the user to distinguish between visually similar or identical glyphs (homoglyphs), which may cause the user to misinterpret a glyph and perform an unintended, insecure action.
Business impact
What CWE-1007 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.
- Other
- Hide Activities
Integrity
Data, pages or code changed
Prices, orders, content or the code your site runs can be altered without your approval.
- Other
- Hide Activities
Free security check
Is CWE-1007 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-1007
Insufficient Visual Distinction of Homoglyphs Presented to User
The product displays information or identifiers to a user, but the display mechanism does not make it easy for the user to distinguish between visually similar or identical glyphs (homoglyphs), which may cause the user to misinterpret a glyph and perform an unintended, insecure action.
Adversaries can exploit this visual similarity for attacks such as phishing, e.g. by providing a link to an attacker-controlled hostname that looks like a hostname that the victim trusts. In a different use of homoglyphs, an adversary may create a back door username that is visually similar to the username of a regular user, which then makes it more difficult for a system administrator to detect the malicious username while reviewing logs.
Also known as: Homograph Attack
Prevention
How to fix CWE-1007, phase by phase
Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.
- 01
Implementation
- Use a browser that displays Punycode for IDNs in the URL and status bars, or which color code various scripts in URLs. Due to the prominence of homoglyph attacks, several browsers now help safeguard against this attack via the use of Punycode. For example, Mozilla Firefox and Google Chrome will display IDNs as Punycode if top-level domains do not restrict which characters can.
- Use an email client that has strict filters and prevents messages that mix character sets to end up in a user’s inbox. Certain email clients such as Google’s GMail prevent the use of non-Latin characters in email addresses or in links contained within emails. This helps prevent homoglyph attacks by flagging these emails and redirecting them to a user’s spam folder.
Detection and evidence
How CWE-1007 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
How it is detected
- Manual Dynamic AnalysisIf utilizing user accounts, attempt to submit a username that contains homoglyphs. Similarly, check to see if links containing homoglyphs can be sent via email, web browsers, or other mechanisms.
Real vulnerabilities it caused
- CVE-2013-7236web forum allows impersonation of users with homoglyphs in account names
- CVE-2012-0584Improper character restriction in URLs in web browser
- CVE-2009-0652Incomplete denylist does not include homoglyphs of "/" and "?" characters in URLs
- CVE-2017-5015web browser does not convert hyphens to punycode, allowing IDN spoofing in URLs
- CVE-2005-0233homoglyph spoofing using punycode in URLs and certificates
- CVE-2005-0234homoglyph spoofing using punycode in URLs and certificates
How we fix it
From finding to fixed: how Codefreex closes CWE-1007
- 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.
- 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.
- 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.
- 04
Keep it fixed
Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.
Website SecurityPenetration TestingMalware Removal & Hack RepairWordPress Maintenance
Related weaknesses
Weaknesses related to CWE-1007
FAQ
CWE-1007: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
What is CWE-1007?
CWE-1007, “Insufficient Visual Distinction of Homoglyphs Presented to User”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product displays information or identifiers to a user, but the display mechanism does not make it easy for the user to distinguish between visually similar or identical glyphs (homoglyphs), which may cause the user to misinterpret a glyph and perform an unintended, insecure action.
How serious is CWE-1007?
MITRE rates the likelihood of exploit as Medium. It can affect integrity, confidentiality, with impacts such as other, varies by context, hide activities. The real risk depends on where the weakness sits and what data or functions it exposes.
How do you prevent CWE-1007?
Use a browser that displays Punycode for IDNs in the URL and status bars, or which color code various scripts in URLs. Due to the prominence of homoglyph attacks, several browsers now help safeguard against this attack via the use of Punycode. For example. Use an email client that has strict filters and prevents messages that mix character sets to end up in a user’s inbox. Certain email clients such as Google’s GMail prevent the use of non-Latin.
Can Codefreex check my site for CWE-1007?
Yes. A senior engineer reviews your site, store or app for CWE-1007 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-1007 affect?
MITRE lists it as applicable to Web Based. 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-1007 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
- Emailhello@codefreex.com
- CallUSA +1 (209) 375-3475 · India +91 790 3375 530
- Prefer to talk?Book a 30-minute call
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.