CVE-2025-52469
Chamilo Lms ≤ 1.11.30
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:NSummary
CVE-2025-52469 is a high-severity Improper Enforcement of Behavioral Workflow (CWE-841) vulnerability in Chamilo Chamilo Lms. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique External Remote Services (T1133); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and IA-11 (Re-authentication) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-52469 is a logic vulnerability in the friend request workflow of Chamilo's social network module, affecting the open-source learning management system Chamilo prior to version 1.11.30. An authenticated user can directly call an AJAX endpoint to forcibly add any other user as a friend, bypassing the standard process of sending and awaiting acceptance of friend requests. This flaw even permits adding non-existent users, undermining access control and social interaction logic with potential privacy implications. The vulnerability is rated 7.1 on the CVSS v3.1 scale (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N) and maps to CWE-841 (Improper Enforcement of Behavioral Workflow).
Any low-privileged authenticated user on a Chamilo instance can exploit this over the network with low complexity and no user interaction required. Successful exploitation allows the attacker to manipulate the social graph by unilaterally establishing friendships, potentially granting unauthorized access to private profiles, messages, or shared resources tied to the friend relationship. While direct confidentiality impact is low, the high integrity impact disrupts intended social controls, enabling abuse such as spam, harassment, or further reconnaissance in educational environments.
The issue has been addressed in Chamilo version 1.11.30, as detailed in the project's GitHub security advisory (GHSA-m5xj-5xf3-rqch), release notes, and the patching commit. Security practitioners should upgrade to 1.11.30 or later and review access to the social network module's AJAX endpoints.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-208174
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V7.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement can require each successive workflow step to present the proper authorization context before proceeding.
Re-authentication requirements can be placed at critical workflow steps to ensure the actor has performed prior behaviors.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly address proper workflow enforcement during design and coding.
Enforcing authorization policies can include sequence constraints on multi-step actions.
Hardened configuration baselines can embed required workflow ordering rules.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect workflow bypasses but does not enforce them at runtime.
Secure development lifecycle requires explicit workflow enforcement in multi-step processes.
Application security requirements include sequencing and state-transition rules for critical workflows.
Secure architecture principles address proper ordering of security-critical operations.
Secure coding practices can prevent missing workflow checks but do not define the control itself.
Change management can require workflow adherence for changes but is not the primary mitigation.