Use of Web Browser Cache Containing Sensitive Information vulnerability in Drupal Media Alias Display allows
Source GCVE Database
Not known to be exploited : upgrade to 3.0.3 or 2.1.3 when convenient.
Data as of 30 Oct 2026, 07:15 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.0.3, 2.1.3
Exploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Upgrade Media Alias Display to 3.0.3 or 2.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DrupalMedia Alias Display | Affected
| Fixed in
|
| DrupalMedia Alias Display | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, review and correct access control configurations to prevent sensitive data from being cached by browsers. Avoid storing sensitive information in cacheable responses.
Description
A vulnerability in Drupal Media Alias Display allows sensitive information to be stored in the web browser cache due to incorrectly configured access control security levels. This affects versions from 0.0.0 to 2.1.3 and from 3.0.0 to 3.0.3. The issue could lead to exposure of sensitive data through the browser cache.