Skip to content
Fencer Vulns
medium 6.2

CVE-2024-33996 json

moodle: broken access control when setting calendar event type

published 2024-05-31 2 y ago modified 2026-09-08 2 mo ago also BIT-moodle-2024-33996 , EUVD-2024-1420 , GHSA-4qww-rxq6-x7gf

cvss
6.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

Incorrect validation of allowed event types in a calendar web service made it possible for some users to create events with types/audiences they did not have permission to publish to.

Patch / fix

  • packagist moodle/moodle 4.1.10, 4.2.7, 4.3.4
  • bitnami moodle 4.1.10, 4.2.7, 4.3.4
  • moodle moodle 4.1.10, 4.2.7, 4.3.4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-33996 updated

moodle: broken access control when setting calendar event type

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:N
GitHub 3.1 6.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:N
CNA 3.1 6.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:N
OSV 3.1 6.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist moodle/moodle
>=4.3.0, <4.3.4
>=4.2.0, <4.2.7
<4.1.10
4.3.4
4.2.7
4.1.10
bitnami moodle
<4.1.10
>=4.2.0, <4.2.7
>=4.3.0, <4.3.4
4.1.10
4.2.7
4.3.4

Affected products

  • Moodle Moodle

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.