VulnerabilityPublished 16 Jan 2026Updated 20 Jan 2026

CVE-2025-69581: chamilo-lms · Use of Cache Containing Sensitive Information

Affects chamilo-lmsSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 16 Jan 2026
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

Affected software

Product	Affected	Fixed in
GitHubchamilo/chamilo-lms`pkg:github/chamilo/chamilo-lms`Other threats	Affected =1.11.2	Fixed in–

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

AI-suggested

To mitigate CVE-2025-69581, organizations should implement the following specific actions: 1) Configure Chamillo LMS or the underlying web server to include strict cache-control headers (e.g., 'Cache-Control: no-store, no-cache, must-revalidate') on all sensitive endpoints, especially /personal_data, to prevent caching of personal information. 2) Ensure that logout functionality properly invalidates sessions and triggers cache clearing mechanisms on the client side. 3) Educate users to close browser tabs or clear browsing data after logout, particularly on shared devices. 4) Where possible, enforce device-level security policies such as screen locking and session timeouts to reduce unauthorized local access. 5) Monitor for updates or patches from Chamillo LMS developers and apply them promptly once available. 6) Conduct regular security reviews and penetration tests focusing on session management and cache control. 7) Consider deploying Content Security Policy (CSP) headers to limit exposure of sensitive data in the browser environment. These measures go beyond generic advice by focusing on cache-control header configuration and user behavior in shared device contexts.

Description

An issue was discovered in Chamillo LMS 1.11.2. The Social Network /personal_data endpoint exposes full sensitive user information even after logout because proper cache-control is missing. Using the browser back button restores all personal data, allowing unauthorized users on the same device to view confidential information. This leads to profiling, impersonation, targeted attacks, and significant privacy risks.

Impact

For European organizations using Chamillo LMS, this vulnerability poses a significant privacy risk, especially in environments where devices are shared or not physically secured, such as educational institutions, training centers, or corporate learning environments. Unauthorized access to cached personal data can lead to identity theft, profiling, and social engineering attacks targeting employees or students. The exposure of sensitive information may also violate GDPR requirements regarding data protection and secure session management, potentially resulting in regulatory penalties and reputational damage. While the vulnerability does not allow remote exploitation, the risk is heightened in scenarios where devices are shared or left unattended. The inability to fully clear sensitive data after logout undermines user trust and may impact compliance with European data privacy laws.

CWE-524Use of Cache Containing Sensitive Information (opens in a new tab)
Base weakness
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
Architecture and Design
Protect information stored in cache.
Architecture and Design
Do not store unnecessarily sensitive information in the cache.
Architecture and Design
Consider using encryption in the cache.
OWASP ASVS 4.0.3
V8.1.1 (opens in a new tab)
V8.1.2 (opens in a new tab)
Attack patterns
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Jan 2026, 19:51 UTC

WeaknessesCWE-524

Technical details

References

Community reviews

Related threats