Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-43434

0
High
VulnerabilityCVE-2024-43434cvecve-2024-43434
Published: Thu Nov 07 2024 (11/07/2024, 13:28:27 UTC)
Source: CVE Database V5

Description

The bulk message sending feature in Moodle's Feedback module's non-respondents report had an incorrect CSRF token check, leading to a CSRF vulnerability.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/28/2026, 06:28:31 UTC

Technical Analysis

CVE-2024-43434 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Moodle Learning Management System's Feedback module, specifically within the bulk message sending feature of the non-respondents report. The root cause is an incorrect or insufficient CSRF token check, which fails to properly validate the authenticity of requests initiating bulk message sends. This flaw allows an attacker to craft malicious web requests that, when executed by an authenticated Moodle user, cause the system to send bulk feedback messages without the user's consent or knowledge. The vulnerability affects Moodle versions 4.2, 4.3, and 4.4. According to the CVSS v3.1 vector (8.1, high severity), the attack can be performed remotely over the network without privileges but requires user interaction (e.g., clicking a malicious link). The impact includes high confidentiality and integrity loss, as unauthorized messages may disclose sensitive information or manipulate communication flows. Availability is not affected. The vulnerability is categorized under CWE-22, which typically relates to improper access control or path traversal issues, but here it is linked to CSRF token validation failure. No public exploits have been reported yet, but the presence of this vulnerability in widely used Moodle versions makes it a significant risk. Moodle is a popular open-source platform used globally by educational institutions, making this vulnerability relevant to a broad user base.

Potential Impact

The primary impact of CVE-2024-43434 is unauthorized bulk message sending within Moodle's Feedback module, which can lead to significant confidentiality breaches by exposing sensitive feedback or user data to unintended recipients. Integrity is also compromised, as attackers can manipulate communication by sending fraudulent messages on behalf of legitimate users, potentially damaging trust and disrupting feedback processes. Although availability is not directly affected, the reputational damage and potential misuse of the messaging feature can indirectly impact organizational operations. Educational institutions and organizations relying on Moodle for communication and feedback are at risk of targeted phishing, social engineering, or misinformation campaigns leveraging this vulnerability. Since exploitation requires only user interaction without elevated privileges, the attack surface is broad, increasing the likelihood of successful exploitation if mitigations are not applied promptly. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits following public disclosure.

Mitigation Recommendations

To mitigate CVE-2024-43434, organizations should immediately upgrade Moodle to a version where the vulnerability is patched once available. Until patches are released, administrators can implement the following specific measures: 1) Disable or restrict access to the bulk message sending feature in the Feedback module for non-administrative users to reduce exposure. 2) Enforce strict Content Security Policy (CSP) headers to limit the ability of attackers to execute malicious scripts that could trigger CSRF attacks. 3) Educate users about the risks of clicking on unsolicited or suspicious links, especially when logged into Moodle. 4) Monitor Moodle logs for unusual bulk messaging activity that could indicate exploitation attempts. 5) Implement additional CSRF protection mechanisms at the web server or application firewall level, such as validating the Referer header or using custom tokens. 6) Regularly audit and review user permissions to ensure only necessary users have access to sensitive modules. These targeted mitigations complement general security best practices and reduce the risk of exploitation until official patches are deployed.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
fedora
Date Reserved
2024-08-13T07:15:00.598Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6cd6b7ef31ef0b569752

Added to database: 2/25/2026, 9:42:46 PM

Last enriched: 2/28/2026, 6:28:31 AM

Last updated: 4/12/2026, 6:13:38 PM

Views: 20

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses