HTTP/1.1 200 OK Date: Fri, 26 Dec 2025 02:03:22 GMT Accept-Ranges: bytes X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Strict-Transport-Security: max-age=15768000; includeSubDomains; preload X-Frame-Options: SAMEORIGIN Content-Security-Policy: default-src 'self' mitre.org *.mitre.org *.google.com *.withgoogle.com *.googleadservices.com *.google-analytics.com www.googletagmanager.com *.gstatic.com platform.twitter.com syndication.twitter.com www.youtube.com www.youtube-nocookie.com *.osano.com play.vidyard.com; script-src 'self' 'unsafe-inline' 'unsafe-eval' mitre.org *.mitre.org *.google.com *.withgoogle.com *.googleadservices.com *.google-analytics.com www.googletagmanager.com *.gstatic.com platform.twitter.com syndication.twitter.com www.youtube.com www.youtube-nocookie.com *.osano.com play.vidyard.com; style-src 'self' 'unsafe-inline' 'unsafe-eval' mitre.org *.mitre.org *.google.com *.withgoogle.com *.googleadservices.com *.google-analytics.com www.googletagmanager.com *.gstatic.com platform.twitter.com syndication.twitter.com www.youtube.com www.youtube-nocookie.com *.osano.com play.vidyard.com; frame-ancestors 'self'; worker-src blob: Content-Type: text/html Set-Cookie: TS01c40944=0126e415d104abf12cf10de07d981e84bdc02b2c02a60a8540d3fc00d63dd1ff9cff2ffbef75a105fc3faec437984d0ff14eae3b82; Path=/; Domain=.cwe.mitre.org Transfer-Encoding: chunked

	CWE Glossary Definition CWE-525: Use of Web Browser Cache Containing Sensitive Information Weakness ID: 525 Vulnerability Mapping: ALLOWED This CWE ID may be used to map to real-world vulnerabilities Abstraction: Variant Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource. View customized information: Conceptual For users who are interested in more notional aspects of a weakness. Example: educators, technical writers, and project/program managers. Operational For users who are concerned with the practical application and details about the nature of a weakness and how to prevent it from happening. Example: tool developers, security researchers, pen-testers, incident response analysts. Mapping Friendly For users who are mapping an issue to CWE/CAPEC IDs, i.e., finding the most appropriate CWE for a specific issue (e.g., a CVE record). Example: tool developers, security researchers. Complete For users who wish to see all available information for the CWE/CAPEC entry. Custom For users who want to customize what details are displayed. × Edit Custom Filter Conceptual Operational Mapping Friendly Select All Reset Clear Submit Cancel Description The web application does not use an appropriate caching policy that specifies the extent to which each web page and associated form fields should be cached. Common Consequences This table specifies different individual consequences associated with the weakness. The Scope identifies the application security area that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in exploiting this weakness. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a weakness will be exploited to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact. Impact Details Read Application Data Scope: Confidentiality Browsers often store information in a client-side cache, which can leave behind sensitive information for other users to find and exploit, such as passwords or credit card numbers. The locations at most risk include public terminals, such as those in libraries and Internet cafes. Potential Mitigations Phase(s) Mitigation Architecture and Design Protect information stored in cache. Architecture and Design; Implementation Use a restrictive caching policy for forms and web pages that potentially contain sensitive information. Architecture and Design Do not store unnecessarily sensitive information in the cache. Architecture and Design Consider using encryption in the cache. Relationships This table shows the weaknesses and high level categories that are related to this weakness. These relationships are defined as ChildOf, ParentOf, MemberOf and give insight to similar items that may exist at higher and lower levels of abstraction. In addition, relationships such as PeerOf and CanAlsoBe are defined to show similar weaknesses that the user may want to explore. Relevant to the view "Research Concepts" (View-1000) Nature Type ID Name ChildOf Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource. 524 Use of Cache Containing Sensitive Information Modes Of Introduction The different Modes of Introduction provide information about how and when this weakness may be introduced. The Phase identifies a point in the life cycle at which introduction may occur, while the Note provides a typical scenario related to introduction during the given phase. Phase Note Implementation Applicable Platforms This listing shows possible areas for which the given weakness could appear. These may be for specific named Languages, Operating Systems, Architectures, Paradigms, Technologies, or a class of such platforms. The platform is listed along with how frequently the given weakness appears for that instance. Languages Class: Not Language-Specific (Undetermined Prevalence) Technologies Class: Web Based (Often Prevalent) Web Server (Undetermined Prevalence) Weakness Ordinalities Ordinality Description Primary (where the weakness exists independent of other weaknesses) Memberships This MemberOf Relationships table shows additional CWE Categories and Views that reference this weakness as a member. This information is often useful in understanding where a weakness fits within the context of external information sources. Nature Type ID Name MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic. 723 OWASP Top Ten 2004 Category A2 - Broken Access Control MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic. 724 OWASP Top Ten 2004 Category A3 - Broken Authentication and Session Management MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic. 966 SFP Secondary Cluster: Other Exposures MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic. 1348 OWASP Top Ten 2021 Category A04:2021 - Insecure Design MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic. 1403 Comprehensive Categorization: Exposed Resource MemberOf Category - a CWE entry that contains a set of other entries that share a common characteristic. 1441 OWASP Top Ten 2025 Category A06:2025 - Insecure Design Vulnerability Mapping Notes Usage ALLOWED (this CWE ID may be used to map to real-world vulnerabilities) Reason Acceptable-Use Rationale This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities. Comments Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction. Taxonomy Mappings Mapped Taxonomy Name Node ID Fit Mapped Node Name OWASP Top Ten 2004 A2 CWE More Specific Broken Access Control OWASP Top Ten 2004 A3 CWE More Specific Broken Authentication and Session Management Related Attack Patterns CAPEC-ID Attack Pattern Name CAPEC-37 Retrieve Embedded Sensitive Data Content History Submissions Submission Date Submitter Organization 2006-07-19 (CWE Draft 3, 2006-07-19) Anonymous Tool Vendor (under NDA) Modifications Modification Date Modifier Organization 2025-12-11 (CWE 4.19, 2025-12-11) CWE Content Team MITRE updated Applicable_Platforms, Relationships, Weakness_Ordinalities 2023-06-29 CWE Content Team MITRE updated Mapping_Notes 2023-04-27 CWE Content Team MITRE updated Relationships 2021-10-28 CWE Content Team MITRE updated Relationships 2020-02-24 CWE Content Team MITRE updated Description, Name, Relationships 2017-11-08 CWE Content Team MITRE updated Taxonomy_Mappings 2014-07-30 CWE Content Team MITRE updated Relationships 2012-10-30 CWE Content Team MITRE updated Potential_Mitigations 2012-05-11 CWE Content Team MITRE updated Relationships 2011-06-27 CWE Content Team MITRE updated Common_Consequences 2011-06-01 CWE Content Team MITRE updated Common_Consequences 2011-03-29 CWE Content Team MITRE updated Name 2009-10-29 CWE Content Team MITRE updated Common_Consequences, Other_Notes, Potential_Mitigations 2008-09-08 CWE Content Team MITRE updated Relationships, Other_Notes, Taxonomy_Mappings 2008-07-01 Eric Dalci Cigital updated Potential_Mitigations, Time_of_Introduction Previous Entry Names Change Date Previous Entry Name 2011-03-29 Information Leak Through Browser Caching 2020-02-24 Information Exposure Through Browser Caching More information is available — Please edit the custom filter or select a different filter.