Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-200 (信息暴露) — Vulnerability Class 2750

2750 vulnerabilities classified as CWE-200 (信息暴露). AI Chinese analysis included.

CWE-200 represents a critical information disclosure weakness where software inadvertently reveals sensitive data to unauthorized entities. This vulnerability is typically exploited by attackers who leverage insufficient access controls, insecure direct object references, or verbose error messages to harvest credentials, personal identifiable information, or internal system details. By analyzing network traffic or manipulating application inputs, adversaries can extract this exposed data to facilitate further attacks, such as identity theft or privilege escalation. To mitigate this risk, developers must implement strict access control mechanisms, ensuring that data retrieval is validated against user permissions. Additionally, employing robust encryption for data at rest and in transit, along with sanitizing error outputs to prevent information leakage, significantly reduces the attack surface. Regular security audits and adherence to the principle of least privilege further ensure that sensitive information remains protected from unauthorized exposure.

MITRE CWE Description
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include: private, personal information, such as personal messages, financial data, health records, geographic location, or contact details system status and environment, such as the operating system and installed packages business secrets and intellectual property network status and configuration the product's own code or internal state metadata, e.g. logging of connections or message headers indirect information, such as a discrepancy between two internal operations that can be observed by an outsider Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include: the product's own users people or organizations whose information is created or used by the product, even if they are not direct product users the product's administrators, including the admins of the system(s) and/or networks on which the product operates the developer Information exposures can occur in different ways: the code explicitly inserts sensitive information into …
Common Consequences (1)
ConfidentialityRead Application Data
Mitigations (1)
Architecture and DesignCompartmentalize 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 privilege separatio…
Examples (2)
The following code checks validity of the supplied username and password and notifies the user of a successful or failed login.
my $username=param('username'); my $password=param('password'); if (IsValidUsername($username) == 1) { if (IsValidPassword($username, $password) == 1) { print "Login Successful"; } else { print "Login Failed - incorrect password"; } } else { print "Login Failed - unknown username"; }
Bad · Perl
"Login Failed - incorrect username or password"
Result
This code tries to open a database connection, and prints any exceptions that occur.
try { openDbConnection(); } //print exception message that includes exception message and configuration file location catch (Exception $e) { echo 'Caught exception: ', $e->getMessage(), '\n'; echo 'Check credentials in config file at: ', $Mysql_config_location, '\n'; }
Bad · PHP
CVE IDTitleCVSSSeverityPublished
CVE-2026-33161 Craft CMS: Anonymous "assets/image-editor" calls returns private asset editor metadata to unauthorized users — cms 5.4 -2026-03-24
CVE-2026-33677 Webhook BasicAuth Credentials Exposed to Read-Only Project Collaborators via API — vikunja 6.5 Medium2026-03-24
CVE-2026-4733 Information disclosure in ixray-1.6-stcop — ixray-1.6-stcop 5.3 Medium2026-03-24
CVE-2025-60949 Census CSWeb leaked configuration files — CSWeb 9.1 Critical2026-03-23
CVE-2026-23486 Blinko: Unauthorized User Information Leak — blinko 5.3 -2026-03-23
CVE-2026-27131 Sprig Plugin for Craft CMS potentially discloses sensitive information via Sprig Playground — craft-sprig 5.5 Medium2026-03-23
CVE-2025-13997 King Addons for Elementor <= 51.1.49 - Unauthenticated API Keys Disclosure — King Addons for Elementor – 80+ Elementor Widgets, 4 000+ Elementor Templates, WooCommerce, Mega Menu, Popup Builder 5.3 Medium2026-03-23
CVE-2026-33422 Discourse exposes ip_address of flagged user — discourse 3.5 Low2026-03-20
CVE-2026-33180 HAPI FHIR HTTP authentication leak in redirects — org.hl7.fhir.core 7.5 High2026-03-20
CVE-2026-33041 AVideo has an Unauthenticated Password Hash Oracle via encryptPass.json.php — AVideo 5.3 Medium2026-03-20
CVE-2026-31869 Discourse: Composer mentions endpoint leaks hidden group membership through PM `allowed_names` check — discourse 4.3 -2026-03-20
CVE-2026-30891 Discourse hasUnauthorized Exposure of Private User Action Types — discourse 6.5 -2026-03-20
CVE-2026-29108 Authenticated SuiteCRM Users Can Retrieve The Password Hash of Any User — SuiteCRM-Core 6.5 Medium2026-03-19
CVE-2026-32002 OpenClaw < 2026.2.23 - Sandbox Boundary Bypass via Image Tool workspaceOnly Bypass — OpenClaw 5.3 Medium2026-03-19
CVE-2026-33394 Discourse leaks PM post edits to moderators — discourse 2.7 Low2026-03-19
CVE-2026-33355 Discourse filters whisper posts from private-posts feed — discourse 6.5 Medium2026-03-19
CVE-2026-32099 Discourse prevents hidden profile data leak via user onebox — discourse 4.3 Medium2026-03-19
CVE-2026-23659 Azure Data Factory Information Disclosure Vulnerability — Azure Data Factory 8.6 High2026-03-19
CVE-2026-32865 OPEXUS eComplaint and eCase insecure password reset — eComplaint 9.8 Critical2026-03-19
CVE-2026-2571 Download Manager <= 3.3.49 - Missing Authorization to Authenticated (Subscriber+) User Email Enumeration via 'user' Parameter — Download Manager 4.3 Medium2026-03-19
CVE-2026-33163 Parse Server leaks protected fields via LiveQuery afterEvent trigger — parse-server 6.5 -2026-03-18
CVE-2026-32633 Glances's Browser API Exposes Reusable Downstream Credentials via `/api/4/serverslist` — glances 9.1 Critical2026-03-18
CVE-2026-32609 Glances has Incomplete Secrets Redaction: /api/v4/args Endpoint Leaks Password Hash and SNMP Credentials — glances 7.5 High2026-03-18
CVE-2026-32596 Glances exposes the REST API without authentication — glances 9.1 -2026-03-18
CVE-2026-32266 Google Cloud Storage for Craft CMS has an Information Disclosure Vulnerability — google-cloud 5.3 -2026-03-18
CVE-2026-32265 Amazon S3 for Craft CMS has an Information Disclosure vulnerability — aws-s3 4.3 -2026-03-18
CVE-2026-1267 IBM Planning Analytics Information Disclosure — Planning Analytics Local 6.5 Medium2026-03-17
CVE-2026-28506 Outline's Information Disclosure in Activity Logs allows User Enumeration of Private Drafts — outline 4.3 Medium2026-03-17
CVE-2026-2476 MS Teams plugin sensitive config values not properly masked in support packets — Mattermost 7.6 High2026-03-16
CVE-2026-4218 myAEDES App aedes.me.beta EngageBayUtils.java information disclosure — myAEDES App 2.5 Low2026-03-16

Vulnerabilities classified as CWE-200 (信息暴露) represent 2750 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.