Variant weakness

Incomplete

CWE-525: Use of Web Browser Cache Containing Sensitive Information

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.

Last updated May 1, 2026

29

Recorded CVEs

With this primary weakness

0

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Variant

Abstraction

MITRE classification

Overview

CWE-525 (Use of Web Browser Cache Containing Sensitive Information) is a variant-level software weakness catalogued by MITRE in the Common Weakness Enumeration (CWE). It describes a recurring type of mistake that can lead to exploitable security vulnerabilities.

Real-world CVEs

29 recorded CVEs are caused by CWE-525 (Use of Web Browser Cache Containing Sensitive Information). The highest-severity and most recent are shown first. 7 new CWE-525 CVEs have been recorded so far in 2026 (11 in 2025).

Medium · CVSS 6.2 · EPSS 4th

2026-03-03

CVE-2024-31906

Medium · CVSS 6.2 · EPSS 4th

2025-01-26

CVE-2025-15554

Admin Passwords Cached by Browsers in Truesec LAPSWebUI

Medium · CVSS 6.0 · EPSS 6th

2026-03-16

CVE-2026-41918

Medium · CVSS 5.9 · EPSS 10th

2026-06-02

CVE-2026-41322

@astrojs/node: Cache Poisoning due to incorrect error handling when if-match header is malformed

Medium · CVSS 5.5 · EPSS 18th

2026-04-24

CVE-2024-25142

Medium · CVSS 5.5 · EPSS 28th

2024-06-14

CVE-2026-24437

Tenda W30E V2 Missing Cache Controls for Credential-bearing Pages

Medium · CVSS 4.8 · EPSS 1th

2026-01-26

CVE-2025-62276

Medium · CVSS 4.6 · EPSS 5th

2025-10-31

CVE-2025-36082

IBM OpenPages information disclosure

Medium · CVSS 4.0 · EPSS 6th

2025-09-15

CVE-2025-1348

IBM Sterling B2B Integrator and IBM Sterling File Gateway information disclosure

Medium · CVSS 4.0 · EPSS 21th

2025-06-18

Showing 12 of 29 recorded CWE-525 CVEs. Track new ones as they are published and get AI-written analysis and fixes.

Monitor CWE-525 vulnerabilities

Common consequences

What can happen when CWE-525 is exploited.

Read Application Data

Affects: 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.

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Implementation

Applies to

Technologies

Web Based (Often)

Web Server

How to prevent it

Practical mitigations for CWE-525, grouped by where in the lifecycle they apply.

Architecture and Design

Protect information stored in cache.

Implementation

Use a restrictive caching policy for forms and web pages that potentially contain sensitive information, such as "no-cache" in the Cache-Control header.

Architecture and Design

Do not store unnecessarily sensitive information in the cache.

Architecture and Design

Consider using encryption in the cache.

Illustrative examples

Real CVEs that MITRE cites as examples of this weakness.

CVE-2024-30127 — Product does not set the "no-cache" option in the HTTP Cache-Control, allowing sensitive information to be cached
CVE-2024-45314 — Login form for an application development framework does not set "no-cache" and other options in the HTTP Cache-Control header, allowing sensitive information to be cached

Terminology & mappings

Mapped taxonomies

OWASP Top Ten 2004: Broken Access Control (A2) — CWE More Specific fit
OWASP Top Ten 2004: Broken Authentication and Session Management (A3) — CWE More Specific fit

Attack patterns

CAPEC attack patterns that exploit this weakness.

CAPEC-37: Retrieve Embedded Sensitive Data

Frequently asked questions

Common questions about CWE-525.

What is CWE-525?

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.

What CVEs are caused by CWE-525?

29 recorded CVEs are attributed to CWE-525, including CVE-2025-48947, CVE-2026-27514, CVE-2025-36364.

Is CWE-525 part of the OWASP Top 10?

CWE-525 maps to OWASP Top Ten 2004: Broken Access Control (A2) in the OWASP security taxonomy.

How do you prevent CWE-525?

Protect information stored in cache.

What are the consequences of CWE-525?

Exploiting CWE-525 can lead to: Read Application Data.

Is CWE-525 actively exploited?

29 recorded CVEs are caused by CWE-525; none are currently in CISA's KEV catalog of actively exploited flaws.

References

Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.

Stay ahead of CWE-525

Get alerted the moment a new CWE-525 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.

Start free See pricing

Overview

Real-world CVEs

Common consequences

How it happens

When it is introduced

Applies to

How to prevent it

Illustrative examples

Related weaknesses

Parent

Terminology & mappings

Mapped taxonomies

Attack patterns

Frequently asked questions

What is CWE-525?

What CVEs are caused by CWE-525?

Is CWE-525 part of the OWASP Top 10?

How do you prevent CWE-525?

What are the consequences of CWE-525?

Is CWE-525 actively exploited?

References

Stay ahead of CWE-525