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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

3255 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)
Confidentiality Read Application Data
Mitigations (1)
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 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 ID Title CVSS Severity Published
CVE-2026-75918 phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File — phpMyFAQ 8.8 High 2026-08-19
CVE-2026-53959 4gaBoards: Mass Information Disclosure (Internal PII Leakage) on /api/users to any authenticated user — 4gaBoards 6.5 Medium 2026-08-18
CVE-2026-76041 Google Chrome 信息泄露漏洞 — Chrome - - 2026-08-18
CVE-2026-62988 Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints — froxlor 9.0 Critical 2026-08-18
CVE-2026-63640 MagicMirror socket payload secret placeholder expansion can disclose SECRET_* environment variables — MagicMirror 4.3 Medium 2026-08-18
CVE-2026-75915 CodeWhale before 0.8.64 Environment Variable Leak via js_execution — CodeWhale 7.5 High 2026-08-18
CVE-2026-62684 File Browser: Share API exposes the password hash and bypass token — filebrowser 2.7 Low 2026-08-18
CVE-2026-69189 Hoppscotch: Cross-user private data exposure and UserHistory IDOR via team GraphQL resolvers — hoppscotch 7.6 High 2026-08-18
CVE-2026-75839 ArcadeDB before 26.8.1 Information Disclosure via Cluster Endpoints — arcadedb 4.3 Medium 2026-08-18
CVE-2026-75587 Plaintext pre-auth secret exposure via Desktop App diagnostics report — Mattermost 3.6 Low 2026-08-17
CVE-2026-71424 Onyx: Cross-user OAuth-token leak via /api/mcp/servers* for per-user MCP servers — onyx 9.6 Critical 2026-08-17
CVE-2026-57485 Stirling-PDF: Internal Service Account API Key Disclosure via Pipeline Endpoint — Stirling-PDF 8.5 High 2026-08-17
CVE-2026-68520 Glances: as_dict_secure() Value-Level Bypass Leaks Credentials in URL Values via /api/4/config — glances 5.3 Medium 2026-08-17
CVE-2026-64859 New API: User List API Leaks Root User Access Token Leading to Privilege Escalation — new-api 9.1 Critical 2026-08-17
CVE-2026-49301 Huawei HarmonyOS 信息泄露漏洞 — HarmonyOS 6.2 Medium 2026-08-17
CVE-2026-49302 Huawei HarmonyOS 信息泄露漏洞 — HarmonyOS 6.2 Medium 2026-08-17
CVE-2026-49307 Huawei HarmonyOS 信息泄露漏洞 — HarmonyOS 6.2 Medium 2026-08-17
CVE-2026-19992 Orange View Limited DualSafe Password Manager & Digital Vault Extension postMessage-based Bridge information disclosure — DualSafe Password Manager & Digital Vault Extension 3.1 Low 2026-08-17
CVE-2026-73047 siyuan before v3.7.4 Server-Side Template Injection via attribute-view — siyuan 6.2 Medium 2026-08-15
CVE-2026-19837 Webkul Bagisto Customer Search search information disclosure — Bagisto 2.7 Low 2026-08-14
CVE-2026-66272 Dell Wyse Management Suite 信息泄露漏洞 — Wyse Management Suite (WMS) 5.3 Medium 2026-08-14
CVE-2026-72834 filebrowser before 2.63.19 Permission Bypass via checksum — filebrowser 4.3 Medium 2026-08-14
CVE-2026-73304 Budibase: SSO OAuth2 Token Leakage via User Metadata Endpoints to Power-Role Users — budibase 4.9 Medium 2026-08-13
CVE-2026-18068 IBM i is Affected By Multiple Vulnerabilities in Java Secure Sockets Extension — i 4.3 Medium 2026-08-13
CVE-2026-72670 Exposure of Sensitive Information to an Unauthorized Actor in Kibana Leading to Disclosure of Fleet Proxy Credentials — Kibana 7.7 High 2026-08-13
CVE-2026-58510 GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private — Gitea Open Source Git Server - - 2026-08-13
CVE-2026-58511 Webhook Authorization Header Returned in Plaintext via API — Gitea Open Source Git Server - - 2026-08-13
CVE-2026-58442 Repository migration SSRF via multi-answer DNS allow-list bypass — Gitea Open Source Git Server - - 2026-08-13
CVE-2026-58434 Private Repository Metadata Remains Accessible After Access Revocation — Gitea Open Source Git Server - - 2026-08-13
CVE-2026-58432 Missing Authorization and Authorization Bypass Through User-Controlled Key and Incorrect Permission Assignment for Critical Resource and Exposure of Sensitive Information to an Unauthorized Actor in code.gitea.io/gitea — Gitea Open Source Git Server - - 2026-08-13

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