How severe is CVE-2024-38277?

CVE-2024-38277 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-38277?

CVE-2024-38277 affects the following packages: moodle/moodle (Packagist), moodle/moodle (Packagist), moodle/moodle (Packagist), moodle/moodle (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-38277?

Update moodle/moodle to 4.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-38277 is resolved across your whole dependency graph.

How do I detect CVE-2024-38277 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moodle/moodle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-38277 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-38277 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-38277 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-38277?

CVE-2024-38277 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-38277?

CVE-2024-38277 is classified as CWE-324 (CWE-324), CWE-326 (CWE-326). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-38277 published, and has it been updated?

CVE-2024-38277 was published on June 18, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2024-38277 — moodle

MEDIUMFix: moodle/moodle@0caedaa

CVE-2024-38277 is a medium-severity (CVSS 5.4) CWE-324 vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.

moodle: QR login key and auto-login key for the Moodle mobile app should be generated as separate keys

Also known asBIT-moodle-2024-38277GHSA-r82w-3phg-qvr4

Published

Jun 18, 2024

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-38277.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk+0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘moodle/moodle🐘moodle/moodle🐘moodle/moodle🐘moodle/moodle

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A unique key should be generated for a user's QR login key and their auto-login key, so the same key cannot be used interchangeably between the two.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	≥ 4.4.0-beta&&< 4.4.1	4.4.1`composer require moodle/moodle:^4.4.1`
🐘Packagist	`moodle/moodle`	≥ 4.3.0-beta&&< 4.3.5	4.3.5`composer require moodle/moodle:^4.3.5`
🐘Packagist	`moodle/moodle`	≥ 4.2.0-beta&&< 4.2.8	4.2.8`composer require moodle/moodle:^4.2.8`
🐘Packagist	`moodle/moodle`	all versions	4.1.11`composer require moodle/moodle:^4.1.11`

Affected Products

2 products · 6 configurations

fedorafedoraproject

2 versions

3940

Application

moodlemoodle

≥ 4.3.0 && < 4.3.5

1 version

4.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moodle/moodle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update moodle/moodle to 4.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-38277 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions