Skip to content
Fencer Vulns
low 3.3

CVE-2023-5548 json

Moodle: cache poisoning risk with endpoint revision numbers

published 2023-11-09 2 y ago modified 2026-09-10 1 mo ago also BIT-moodle-2023-5548 , EUVD-2023-2954 , GHSA-cwh2-q44x-5w3c

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

Summary

Stronger revision number limitations were required on file serving endpoints to improve cache poisoning protection.

Patch / fix

  • packagist moodle/moodle 4.3.0-rc2
  • bitnami moodle 3.9.24, 3.11.17, 4.0.11, 4.1.6, 4.2.3
  • moodle moodle 3.9.24, 3.11.17, 4.0.11, 4.1.6, 4.2.3

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-2023-5548 updated cvss 3.3

moodle: Cache poisoning risk with endpoint revision numbers

  • 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

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist moodle/moodle
<4.3.0-rc2
4.3.0-rc2
bitnami moodle
<3.9.24
>=3.11.0, <3.11.17
>=4.0.0, <4.0.11
>=4.1.0, <4.1.6
>=4.2.0, <4.2.3
3.9.24
3.11.17
4.0.11
4.1.6
4.2.3

Classification

Weakness
  • CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data
  • CWE-345 Insufficient Verification of Data Authenticity

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.