VulnerabilityPublished 18 Nov 2025Updated 16 Jan 2026

CVE-2025-13083: Drupal core · Use of Web Browser Cache Containing Sensitive Information

Affects Drupal coreSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low · fixed in 11.2.8 : update Drupal core when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.2.8, 11.1.9, 10.5.6 +1

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade drupal/core to 11.2.8, 11.1.9, 10.5.6 or 10.4.9.

Affected software

Product	Affected	Fixed in
Packagistdrupal/core`pkg:composer/drupal/core`Other threats	Affected <10.4.9 <10.5.6 <11.1.9 <11.2.8	Fixed in 10.4.9 10.5.6 11.1.9 11.2.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Drupal core to the fixed versions: at least 10.4.9, 10.5.6, 11.1.9, 11.2.8, or 7.103 depending on the version in use.
Review and enforce strict cache-control HTTP headers (e.g., Cache-Control: no-store, no-cache, private) on pages or API responses containing sensitive information to prevent browser caching.
Audit access control configurations within Drupal to ensure sensitive content is properly restricted and not inadvertently exposed to unauthorized users or cached.
Implement Content Security Policy (CSP) headers to reduce the risk of client-side data leakage.
Educate developers and administrators on secure caching practices and the risks of sensitive data caching.
Monitor web server and application logs for unusual access patterns that might indicate attempts to exploit cached data.
For highly sensitive environments, consider disabling browser caching entirely for authenticated or sensitive sessions.
Conduct regular security assessments and penetration testing focusing on caching and access control mechanisms.

Description

Use of Web Browser Cache Containing Sensitive Information vulnerability in Drupal Drupal core allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Drupal core: from 8.0.0 before 10.4.9, from 10.5.0 before 10.5.6, from 11.0.0 before 11.1.9, from 11.2.0 before 11.2.8, from 7.0 before 7.103.

Impact

For European organizations, this vulnerability primarily threatens the confidentiality of sensitive information processed or displayed by Drupal-based websites or applications. Organizations handling personal data, financial information, or confidential business data through Drupal platforms could inadvertently expose such data to unauthorized parties if browser caches are accessed by attackers or unauthorized users. This risk is heightened in environments where client devices are shared, compromised, or subject to network interception. Although the vulnerability does not affect data integrity or availability, the leakage of sensitive information could lead to privacy violations, regulatory non-compliance (e.g., GDPR), reputational damage, and potential legal consequences. The low CVSS score reflects the requirement for high attack complexity and no direct integrity or availability impact, but the widespread use of Drupal in Europe means the aggregate risk is non-negligible. Organizations with public-facing Drupal sites or intranet portals should prioritize patching and configuration reviews to mitigate this exposure.

CWE-525Use of Web Browser Cache Containing Sensitive Information (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
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.
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.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.2.1 (opens in a new tab)
V8.1.1 (opens in a new tab)
V8.1.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

drupal.org/sa-core-2025-008 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Jan 2026, 07:22 UTC

WeaknessesCWE-525

Technical details

References

Community reviews

Related threats