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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

3251 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-61802 Wazuh discloses cleartext cluster key to low-privilege API users via GET /cluster/local/config — wazuh 6.5 Medium 2026-08-27
CVE-2026-78174 WatchGuard Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs — Dimension 9.3 Critical 2026-08-27
CVE-2026-61783 Wazuh: RBAC permission-effect check in mask_sensitive_config allows low-privilege users to read cluster.key — wazuh 7.0 High 2026-08-27
CVE-2026-77438 Trilium unauthenticated share-search discloses password-protected and hidden shared notes — Trilium 7.5 High 2026-08-27
CVE-2026-81679 OpenRemote before 1.28.0 Cross-Realm Information Disclosure via Notification API — openremote 7.7 High 2026-08-27
CVE-2026-81101 Airtable MCP CLI before 0.2.5 Credential Disclosure via Unvalidated Configured Endpoint — airtable-mcp-cli 6.5 Medium 2026-08-27
CVE-2026-77507 Weblate: Object-scoped RSS feeds disclose private change history to unauthorized users — weblate 5.3 Medium 2026-08-26
CVE-2026-62249 Weblate: Restricted-component change history leaked to non-member project users through the nested `GET /api/projects/{slug}/changes/` endpoint — weblate 4.3 Medium 2026-08-26
CVE-2026-48786 Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint — fleet 6.5 Medium 2026-08-26
CVE-2026-54553 Starlette-Admin: Unvalidated `order_by` parameter allows ordering by hidden columns (info-exposure oracle) and HTTP 500 DoS — starlette-admin 5.4 Medium 2026-08-26
CVE-2026-80194 Kimai before 2.64.0 Missing Authorization via ProjectViewController export — kimai 4.3 Medium 2026-08-25
CVE-2026-62865 TypeBot: Arbitrary server file read via Send Email block attachment path — typebot.io 8.7 High 2026-08-25
CVE-2026-78957 iOS版Chrome<152.0.7977.65信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-78981 Chrome Mobile iOS <=152.0.7977.65信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79207 Chrome iOS <152.0.7977.65 信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79125 Chrome<152.0.7977.65 XR信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79246 Chrome<152.0.7977.65 DataTransfer信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79018 Google Chrome <152.0.7977.65 折叠API信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-78896 Chrome 152.0.7977.65前存储访问API信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79147 Skia信息泄露漏洞(Google Chrome <152.0.7977.65) — Chrome - - 2026-08-25
CVE-2026-79001 Chrome Mac 152.0.7977.65前蓝牙信息泄露 — Chrome - - 2026-08-25
CVE-2026-79055 Chrome <152.0.7977.65 Android 本地信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79124 Chrome <152.0.7977.65 Android Intent信息泄露 — Chrome - - 2026-08-25
CVE-2026-79185 Chrome <152.0.7977.65 DOM信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79075 Chrome低于152.0.7977.65位置信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-78960 Chrome<152.0.7977.65插件信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79034 Chrome<152.0.7977.65 CORS信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79252 Chrome <152.0.7977.65 跨源数据泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79220 Chrome < 152.0.7977.65 信息泄露漏洞 — Chrome - - 2026-08-25
CVE-2026-79059 Chrome < 152.0.7977.65 BFCache信息泄露漏洞 — Chrome - - 2026-08-25

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