Security weaknessCWE Top 25 · #20
CWE-200 Information disclosure
Your site reveals private data or technical details to people who were never meant to see them.
- Senior security engineers
- 540+ projects delivered
- Reply within one business day
Quick answer
What is CWE-200?
Exposure of Sensitive Information to an Unauthorized Actor: The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Business impact
What CWE-200 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 Application Data
In plain English
What Information disclosure means for your business
- 540+projects delivered
- 9+years in business
- 23+certified experts
A senior engineer replies within one business day.
Information exposure happens when your website or app gives out data to someone who is not authorized to have it. Sometimes the data is plainly sensitive, such as customer emails, order history or payment details. Sometimes it is technical, such as error messages that reveal file paths, database names or software versions. Either way, the system shares more than the person asking should receive.
For a business, leaked personal data can mean privacy complaints, legal obligations to notify customers and lost trust. Leaked technical details matter too, because they give an attacker a map of your system and make other attacks easier to plan. Exposure is rarely one dramatic failure. It is usually a collection of small leaks: a verbose error page, an API that returns extra fields, a forgotten backup file.
Where it shows up
- Error pages and debug modes left on in production that print stack traces, database queries, file paths or environment settings to any visitor.
- API responses that return whole database records, including emails, phone numbers or internal notes, when the page only needs a name and a price.
- Backup archives, log files, configuration files and source control folders left inside the public web directory where they can be downloaded.
- Login, signup and password reset forms that respond differently for existing accounts, which lets anyone confirm whether a given email address is registered.
Free security check
Is CWE-200 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-200
Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Also known as: Information Disclosure, Information Leak
Fix it
How to fix Information disclosure
Practical steps in priority order. Share them with your developer or agency.
Turn off debug output in production
Disable debug mode and detailed error display on live sites. Show visitors a generic error page, and send the full details to a private log or monitoring tool that only your team can read.
Return only the fields needed
Build API responses from an explicit list of permitted fields instead of serializing whole database objects. Review each endpoint for personal data, internal identifiers and notes that the caller has no reason to receive.
Remove sensitive files from the web root
Keep backups, logs, environment files and version control folders outside the publicly served directory. Block direct access to them at the web server, and turn off directory listing so folders cannot be browsed.
Give uniform responses on account forms
Make login, signup and password reset return the same message and take similar time whether or not the account exists. This stops the forms from confirming which email addresses are registered.
Classify data and limit access
Identify which data is sensitive, then store less of it, encrypt it at rest, mask it in logs and admin screens, and restrict database and dashboard access to the people and services that need it.
Signs you may be affected
- Visitors see detailed error messages with file paths, query text or software version numbers.
- Your browser’s network tab shows API responses carrying fields the page never displays.
- Search engines have indexed internal documents, staging sites, logs or backup files from your domain.
Questions to ask your developer
- Is debug mode off and are detailed errors hidden on the live site?
- Do our API responses include any fields the front end does not use?
- Are backups, logs or configuration files stored anywhere a browser can reach?
Prevention
What MITRE recommends, phase by phase
Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.
- 01
Architecture and Design
- Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces.
Detection and evidence
How CWE-200 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
How it is detected
- Automated Static Analysis – Binary or BytecodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Bytecode Weakness Analysis – including disassembler + source code weakness analysis Inter-application Flow Analysis
- Dynamic Analysis with Automated Results InterpretationAccording to SOAR [REF-1479], the following detection techniques may be useful: Web Application Scanner Web Services Scanner Database Scanners
- Dynamic Analysis with Manual Results InterpretationAccording to SOAR [REF-1479], the following detection techniques may be useful: Fuzz Tester Framework-based Fuzzer Automated Monitored Execution Monitored Virtual Environment – run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious
- Manual Static Analysis – Source CodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Manual Source Code Review (not inspections)
- Automated Static Analysis – Source CodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Context-configured Source Code Weakness Analyzer Source code Weakness Analyzer
Real vulnerabilities it caused
- CVE-2022-31162Rust library leaks Oauth client details in application debug logs
- CVE-2021-25476Digital Rights Management (DRM) capability for mobile platform leaks pointer information, simplifying ASLR bypass
- CVE-2001-1483Enumeration of valid usernames based on inconsistent responses
- CVE-2001-1528Account number enumeration via inconsistent responses.
- CVE-2004-2150User enumeration via discrepancies in error messages.
- CVE-2005-1205Telnet protocol allows servers to obtain sensitive environment information from clients.
How we fix it
From finding to fixed: how Codefreex closes CWE-200
- 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-200
FAQ
CWE-200: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
How serious is information disclosure for a business?
It depends on what leaks. Exposed customer records can trigger privacy obligations, complaints and lasting damage to trust. Exposed technical details are less visible but still harmful, because they help an attacker choose and plan the next step. MITRE rates the likelihood of exploitation as high, so it is worth checking for leaks before someone else does.
How do I prevent sensitive information from leaking?
Start by knowing what sensitive data you hold and where it travels. Turn off debug output on live sites, return only the fields each screen needs, and keep backups and logs out of public folders. Review new features and plugins for what they reveal. Regular checks matter, because leaks tend to appear gradually as a site grows.
Is showing a software version number really a risk?
On its own, a version number is a minor leak. The concern is that it tells an attacker exactly which known flaws to try, which saves them effort. Hiding versions does not replace updating your software, but removing unnecessary detail from headers, error pages and page source is a simple way to give away less.
What is CWE-200?
CWE-200, “Exposure of Sensitive Information to an Unauthorized Actor”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How serious is CWE-200?
MITRE rates the likelihood of exploit as High. It can affect confidentiality, with impacts such as read application data. It ranks number 20 on the 2025 CWE Top 25 Most Dangerous Software Weaknesses. The real risk depends on where the weakness sits and what data or functions it exposes.
How do you prevent CWE-200?
Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that.
Can Codefreex check my site for CWE-200?
Yes. A senior engineer reviews your site, store or app for CWE-200 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-200 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.