VulnerabilityPublished 2 Mar 2026

CVE-2025-52469: chamilo-lms · Improper Enforcement of Behavioral Workflow

Affects chamilo-lmsSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 1.11.30 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.1High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.11.30

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 2 Mar 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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 chamilo-lms and chamilo/chamilo-lms to 1.11.30.

Affected software

Product	Affected	Fixed in
chamilochamilo-lms	Affected <1.11.30	Fixed in 1.11.30
GitHubchamilo/chamilo-lms`pkg:github/chamilo/chamilo-lms`Other threats	Affected <1.11.30	Fixed in 1.11.30

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-52469, organizations should immediately upgrade Chamilo LMS to version 1.11.30 or later, where the vulnerability is patched. Until the upgrade is applied, administrators should consider disabling the social network module or restricting access to the friend request functionality to trusted users only. Implementing strict authentication and monitoring for unusual friend addition patterns can help detect exploitation attempts. Additionally, reviewing and tightening access control policies around AJAX endpoints and validating all client-side requests on the server side can prevent similar workflow bypass issues. Regularly auditing user relationships and logs for anomalies can also aid in early detection. Educating users about the risks of unauthorized friend connections and encouraging reporting of suspicious activity will enhance overall security posture. Finally, applying the principle of least privilege to user roles within the LMS reduces the risk of exploitation by limiting who can access social features.

Description

Chamilo is a learning management system. Prior to version 1.11.30, a logic vulnerability in the friend request workflow of Chamilo’s social network module allows an authenticated user to forcibly add any user as a friend by directly calling the AJAX endpoint. The attacker can bypass the normal flow of sending and accepting friend requests, and even add non-existent users. This breaks access control and social interaction logic, with potential privacy implications. This issue has been patched in version 1.11.30.

Impact

The primary impact of CVE-2025-52469 is the unauthorized manipulation of social connections within the Chamilo LMS platform. Attackers can forcibly add users as friends without their consent, which can lead to privacy breaches by exposing personal or academic information intended only for trusted contacts. This undermines the trust model of the social network module and can facilitate further social engineering or targeted attacks within the LMS community. Although the vulnerability does not directly compromise system availability or allow remote code execution, the integrity of user relationships and access controls is compromised. Organizations using affected versions may face reputational damage, loss of user trust, and potential compliance issues related to data privacy regulations. The ability to add non-existent users may also cause data inconsistencies or application errors. Since the flaw requires authenticated access, insider threats or compromised accounts can exploit this vulnerability more easily. Overall, the impact is significant in environments where social networking features are critical for collaboration and communication.

CWE-841Improper Enforcement of Behavioral Workflow (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence or timeframe.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.1 (opens in a new tab)
V11.1.5 (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 9 Mar 2026, 17:17 UTC

WeaknessesCWE-841

Technical details

References

Community reviews

Related threats