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

Goal: 1000 CNY · Raised: 1020 CNY

100%

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

2793 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-2024-30263 The PDF Viewer macro can be used to view PDF attachments with restricted access — macro-pdfviewer 7.7 High2024-04-04
CVE-2024-31207 Vite's `server.fs.deny` did not deny requests for patterns with directories — vite 5.9 Medium2024-04-04
CVE-2024-3262 Information exposure vulnerability in Request Tracker (RT) — Request Tracker 5.5 Medium2024-04-04
CVE-2024-3274 D-Link DNS-320L/DNS-320LW/DNS-327L HTTP GET Request info.cgi information disclosure — DNS-320L 5.3 Medium2024-04-04
CVE-2023-38729 IBM Db2 information disclosure — Db2 for Linux, UNIX and Windows 6.8 Medium2024-04-03
CVE-2024-2931 WPFront User Role Editor <= 3.2.1.11184 - Limited Information Exposure — WPFront User Role Editor 4.3 Medium2024-04-02
CVE-2024-3160 Intelbras HDCVI 1016 HTTP GET Request cap.js information disclosure — MHDX 1004 5.3 Medium2024-04-02
CVE-2024-30469 WordPress Wholesale For WooCommerce plugin <= 2.3.0 - Unauthenticated Sensitive Data Exposure vulnerability — Wholesale For WooCommerce 5.3 Medium2024-03-29
CVE-2024-29898 Oversight in fix for GHSA-4rcf-3cj2-46mq may have exposed suppressed wiki requests on private wikis — CreateWiki 4.9 Medium2024-03-28
CVE-2024-29897 CreateWiki Leak of suppressed wiki requests outside of `CreateWikiGlobalWiki` — CreateWiki 4.9 Medium2024-03-28
CVE-2023-52231 WordPress Booster Plus for WooCommerce plugin < 7.1.2 - Auth. Sensitive Data Exposure vulnerability — Booster Plus for WooCommerce 6.5 Medium2024-03-28
CVE-2023-52234 WordPress Booster Elite for WooCommerce plugin < 7.1.2 - Auth. Sensitive Data Exposure vulnerability — Booster Elite for WooCommerce 6.5 Medium2024-03-28
CVE-2024-28247 Pihole Authenticated Arbitrary File Read with root privileges — pi-hole 7.6 High2024-03-27
CVE-2023-27630 WordPress Community by PeepSo plugin <= 6.0.9.0 - Server Information Disclosure — Community by PeepSo 5.3 Medium2024-03-26
CVE-2023-25965 WordPress Upload Resume plugin <= 1.2.0 - Sensitive Data Exposure vulnerability — Upload Resume 5.9 Medium2024-03-26
CVE-2024-29197 Pimcore Preview Documents are not restricted to logged in users anymore — pimcore 6.5 Medium2024-03-26
CVE-2024-29883 CreateWiki's wiki request suppression ignores the suppression settings set by the suppressor — CreateWiki 4.9 Medium2024-03-26
CVE-2024-30233 WordPress WholesaleX plugin <= 1.3.1 - Sensitive Data Exposure on User Export vulnerability — WholesaleX 6.5 Medium2024-03-26
CVE-2024-29199 Unauthenticated views may expose information to anonymous users — nautobot 3.7 Low2024-03-26
CVE-2023-48296 OroPlatform's storefront user can access history and most viewed data from matching back-office user with the same ID — orocommerce 4.3 Medium2024-03-25
CVE-2023-45824 OroPlatform's pinned entity creation form shows pages of other users — platform 4.3 Medium2024-03-25
CVE-2022-32751 IBM Security Verify Directory information disclosure — Security Verify Directory 5.3 Medium2024-03-22
CVE-2024-2728 Information exposure vulnerability in the CIGESv2 system — CIGESv2 4.1 Medium2024-03-22
CVE-2024-2725 Exposure of Sensitive Information vulnerability in the CIGESv2 system — CIGESv2 7.5 High2024-03-22
CVE-2024-2080 LiquidPoll – Polls, Surveys, NPS and Feedback Reviews <= 3.3.76 - Information Exposure — LiquidPoll – Polls, Surveys, NPS and Feedback Reviews 4.3 Medium2024-03-22
CVE-2024-27277 IBM Storage Protect Plus Server information disclosure — Storage Protect Plus Server 6.2 Medium2024-03-21
CVE-2024-2740 Exposure of Sensitive Information to an Unauthorized Actor in Planet IGS-4215-16T2S — IGS-4215-16T2S 7.7 High2024-03-21
CVE-2024-29036 Saleor Storefront session leak in cache — storefront 4.3 Medium2024-03-20
CVE-2024-27286 Moving single messages from public to private streams leaves them accessible — zulip 6.5 Medium2024-03-20
CVE-2024-1477 Easy Maintenance Mode <= 1.4.2 - Information Exposure — Easy Maintenance Mode 5.3 Medium2024-03-20

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