CWE-539: Use of Persistent Cookies Containing Sensitive Information
The web application uses persistent cookies, but the cookies contain sensitive information.
Last updated
Overview
Cookies are small bits of data that are sent by the web application but stored locally in the browser. This lets the application use the cookie to pass information between pages and store variable information. The web application controls what information is stored in a cookie and how it is used. Typical types of information stored in cookies are session identifiers, personalization and customization information, and in rare cases even usernames to enable automated logins. There are two different types of cookies: session cookies and persistent cookies. Session cookies just live in the browser's memory and are not stored anywhere, but persistent cookies are stored on the browser's hard drive. This can cause security and privacy issues depending on the information stored in the cookie and how it is accessed.
Real-world CVEs
7 recorded CVEs are caused by CWE-539 (Use of Persistent Cookies Containing Sensitive Information). The highest-severity and most recent are shown first. 3 new CWE-539 CVEs have been recorded so far in 2026 (1 in 2025).
- CVE-2025-27673Critical · CVSS 9.1 · EPSS 42th2025-03-05
- CVE-2023-30861High · CVSS 8.7 · EPSS 68th2023-05-02
- CVE-2024-39275High · CVSS 8.5 · EPSS 32th2024-09-27
- CVE-2025-52633
HCL AION is susceptible to Missing Content-Security-Policy
Medium · CVSS 5.3 · EPSS 8th2026-02-03 - CVE-2021-27463Medium · CVSS 5.3 · EPSS 57th2021-05-20
- CVE-2026-24318
Insecure Session Management vulnerability in SAP BusinessObjects Business Intelligence Platform
Medium · CVSS 4.2 · EPSS 6th2026-04-14 - CVE-2026-35192
Session fixation via public cached pages and SESSION_SAVE_EVERY_REQUEST
Low · CVSS 2.3 · EPSS 43th2026-05-05
Common consequences
What can happen when CWE-539 is exploited.
Read Application Data
Affects: Confidentiality
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
Applies to
Technologies
How to prevent it
Practical mitigations for CWE-539, grouped by where in the lifecycle they apply.
Do not store sensitive information in persistent cookies.
How to detect it
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness: High
Attack patterns
CAPEC attack patterns that exploit this weakness.
Frequently asked questions
Common questions about CWE-539.
- What is CWE-539?
- The web application uses persistent cookies, but the cookies contain sensitive information.
- What CVEs are caused by CWE-539?
- 7 recorded CVEs are attributed to CWE-539, including CVE-2025-27673, CVE-2023-30861, CVE-2024-39275.
- How do you prevent CWE-539?
- Do not store sensitive information in persistent cookies.
- How is CWE-539 detected?
- Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
- What are the consequences of CWE-539?
- Exploiting CWE-539 can lead to: Read Application Data.
- Is CWE-539 actively exploited?
- 7 recorded CVEs are caused by CWE-539; none are currently in CISA's KEV catalog of actively exploited flaws.
References
- MITRE CWE definition (CWE-539) (opens in a new tab)
- CWE-539 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
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-539
Get alerted the moment a new CWE-539 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.