Cyber Resilience

CVE-2025-52469

Chamilo Lms ≤ 1.11.30

Public PoC
Published
02 March 2026
Modified
03 March 2026
Patch / advisory
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
EPSS Score 0.0029 21th percentile
Risk Priority 53 floored blend · peak EPSS

Summary

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

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

T1133 External Remote Services Persistence
Adversaries may leverage external-facing remote services to initially access and/or persist within a network.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1657 Financial Theft Impact
Adversaries may steal monetary resources from targets through extortion, social engineering, technical theft, or other methods aimed at their own financial gain at the expense of the availability of these resources for victims.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34160Same product: Chamilo Chamilo Lms
CVE-2026-33715Same product: Chamilo Chamilo Lms
CVE-2026-32930Same product: Chamilo Chamilo Lms
CVE-2026-33702Same product: Chamilo Chamilo Lms
CVE-2025-50191Same product: Chamilo Chamilo Lms
CVE-2026-30881Same product: Chamilo Chamilo Lms
CVE-2025-50190Same product: Chamilo Chamilo Lms
CVE-2024-30617Same product: Chamilo Chamilo Lms
CVE-2026-33703Same product: Chamilo Chamilo Lms
CVE-2023-34959Same product: Chamilo Chamilo Lms

Affected Assets

chamilo
chamilo lms
≤ 1.11.30

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • 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.

PR.PS-06 mostly match
degrades

Secure development practices directly address proper workflow enforcement during design and coding.

PR.AA-05 partial match
prevents

Enforcing authorization policies can include sequence constraints on multi-step actions.

PR.PS-01 partial match
prevents

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.

finds

Security testing can detect workflow bypasses but does not enforce them at runtime.

prevents

Secure development lifecycle requires explicit workflow enforcement in multi-step processes.

prevents

Application security requirements include sequencing and state-transition rules for critical workflows.

prevents

Secure architecture principles address proper ordering of security-critical operations.

prevents

Secure coding practices can prevent missing workflow checks but do not define the control itself.

mitigates

Change management can require workflow adherence for changes but is not the primary mitigation.

References