CVE-2024-30619VulnerabilityPublished 4 Nov 2024Updated 5 Nov 2024

CVE-2024-30619: chamilo-lms · n/a

Affects chamilo-lmsSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: 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: 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: 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 4 Nov 2024
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 2026-10-26.

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 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.26	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-2024-30619, organizations should first apply any official patches or updates provided by Chamilo LMS developers once available. In the absence of immediate patches, administrators should implement strict access controls on the affected AJAX endpoints, restricting access to authenticated and authorized users only. This can be achieved by configuring web server rules (e.g., using .htaccess or firewall rules) to block unauthenticated requests to "/main/inc/ajax/message.ajax.php" and "/main/inc/ajax/online.ajax.php". Additionally, enabling web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting these endpoints can reduce exposure. Monitoring and logging access to these URLs will help detect potential exploitation attempts. Organizations should also review user permissions and session management policies to minimize information leakage. Finally, educating system administrators about this vulnerability and encouraging timely updates will help maintain a secure LMS environment.

Description

Chamilo LMS Version 1.11.26 is vulnerable to Incorrect Access Control. A non-authenticated attacker can request the number of messages and the number of online users via "/main/inc/ajax/message.ajax.php?a=get_count_message" AND "/main/inc/ajax/online.ajax.php?a=get_users_online."

Impact

The primary impact of CVE-2024-30619 is the unauthorized disclosure of sensitive information regarding user activity within the Chamilo LMS environment. Attackers can determine the number of messages and online users without authentication, which could aid in profiling user behavior, timing attacks, or preparing for more sophisticated intrusions. While this vulnerability does not allow direct modification of data or disruption of services, the confidentiality breach can undermine user privacy and organizational trust. Educational institutions and training providers using Chamilo LMS may face reputational damage and potential compliance issues related to data protection regulations. Additionally, attackers might combine this information with other vulnerabilities or social engineering tactics to escalate privileges or conduct targeted attacks. The ease of exploitation and network accessibility increase the risk of automated scanning and mass reconnaissance campaigns targeting vulnerable LMS deployments worldwide.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 12:12 UTC

Technical details

References

Community reviews

Related threats