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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

2752 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-5571 Technostrobe HI-LED-WR120-G2 Configuration Data fs information disclosure — HI-LED-WR120-G2 5.3 Medium2026-04-05
CVE-2026-34947 Discourse: Staged user custom fields are exposed on public invite pages — discourse 4.3AIMediumAI2026-04-03
CVE-2026-27481 Discourse: Hidden tag visibility bypass on tag routes — discourse 5.3AIMediumAI2026-04-03
CVE-2026-5413 Newgen OmniDocs GetWebApiConfiguration information disclosure — OmniDocs 3.7 Low2026-04-02
CVE-2026-5032 W3 Total Cache <= 2.9.3 - Unauthenticated Security Token Exposure via User-Agent Header — W3 Total Cache 7.5 High2026-04-02
CVE-2026-34518 AIOHTTP: Cookie and Proxy-Authorization headers leaked on cross-origin redirect — aiohttp 4.3 -2026-04-01
CVE-2026-3774 Self-Modifications Affecting Altered Printing and Redaction in Foxit PDF Editor — Foxit PDF Editor 4.7 Medium2026-04-01
CVE-2025-71280 XenForo Local Account Page Caching Information Disclosure — XenForo 6.2 Medium2026-04-01
CVE-2026-34215 Parse Server: Auth data exposed via verify password endpoint — parse-server 6.5 -2026-03-31
CVE-2026-33300 Discourse: Hidden group names and access metadata are exposed to moderators through the `category-chatables` endpoint — discourse 4.3 -2026-03-31
CVE-2026-32951 Discourse: Authorization bypass in oneboxer via user-controlled category id — discourse 4.3 Medium2026-03-31
CVE-2026-32620 Discourse: Missing post-level authorization allows whisper metadata disclosure — discourse 4.3 -2026-03-31
CVE-2026-32618 Discourse: Unauthorized channel membership inference via excluded_memberships_channel_id — discourse 4.3 Medium2026-03-31
CVE-2026-32143 Discourse: Admin-only report can be exported by moderators — discourse 6.5 -2026-03-31
CVE-2026-33073 discourse-subscriptions plugin leaking stripe API key in multisite environment — discourse 6.5 -2026-03-31
CVE-2026-4020 Gravity SMTP <= 2.1.4 - Unauthenticated Sensitive Information Exposure via REST API — Gravity SMTP 7.5 High2026-03-31
CVE-2026-5003 PromtEngineer localGPT Web api_server.py handle_index information disclosure — localGPT 5.3 Medium2026-03-28
CVE-2026-1307 Ninja Forms <= 3.14.1 - Authenticated (Contributor+) Sensitive Information Disclosure via Block Editor Token — Ninja Forms – The Contact Form Builder That Grows With You 6.5 Medium2026-03-28
CVE-2026-33981 Changedetection.io Discloses Environment Variables via jq env Builtin in Include Filters — changedetection.io 7.5 -2026-03-27
CVE-2026-33886 Statamic's sensitive configuration values are exposed to content editors via Antlers-enabled fields — cms 6.5 Medium2026-03-27
CVE-2026-31951 LibreChat's MCP Server Header Injection Enables OAuth Token Theft — LibreChat 6.8 Medium2026-03-27
CVE-2025-15381 Unauthorized Access to Tracing and Assessment Endpoints in mlflow/mlflow — mlflow/mlflow 5.4 -2026-03-27
CVE-2025-59031 Open-Xchange OX Dovecot Pro 安全漏洞 — OX Dovecot Pro 4.3 Medium2026-03-27
CVE-2026-33745 cpp-httplib Client Leaks Authentication Credentials to Untrusted Hosts on Cross-Origin HTTP Redirect — cpp-httplib 7.4 High2026-03-27
CVE-2026-1556 Information disclosure via file URI overwrite in File (Field) Paths — Drupal File (Field) Paths 6.5 -2026-03-26
CVE-2025-55265 HCL Aftermarket DPC is affected by File Discovery — Aftermarket DPC 6.5 Medium2026-03-26
CVE-2025-55272 HCL Aftermarket DPC is affected by Banner Disclosure vulnerability — Aftermarket DPC 3.1 Low2026-03-26
CVE-2025-55276 HCL Aftermarket DPC is affected by Internal IP Disclosure vulnerability — Aftermarket DPC 3.1 Low2026-03-26
CVE-2026-4823 Enter Software Iperius Backup NTLM2 information disclosure — Iperius Backup 2.5 Low2026-03-25
CVE-2025-14915 IBM WebSphere Application Server Liberty is affected by a privilege escalation vulnerability — WebSphere Application Server - Liberty 6.5 Medium2026-03-25

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