How severe is CVE-2022-30600?

CVE-2022-30600 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-30600?

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

How do I fix CVE-2022-30600?

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

How do I detect CVE-2022-30600 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-2022-30600 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-2022-30600 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2022-30600, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-30600?

CVE-2022-30600 has an EPSS (Exploit Prediction Scoring System) score of 5.1%, placing it in the 92th 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-2022-30600?

CVE-2022-30600 is classified as CWE-682 (CWE-682). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-30600 published, and has it been updated?

CVE-2022-30600 was published on May 18, 2022 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

CRITICAL severity

CVE-2022-30600 — moodle

CRITICALFix: moodle/moodle@59b5858

CVE-2022-30600 is a critical-severity (CVSS 9.8) CWE-682 vulnerability in moodle/moodle. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for moodle/moodle — see the affected versions and patch details below.

Incorrect Calculation in moodle

Also known asBIT-moodle-2022-30600GHSA-w37f-pvvx-wcwm

Published

May 18, 2022

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

5.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% 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 flaw was found in moodle where logic used to count failed login attempts could result in the account lockout threshold being bypassed.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	≥ 4.0&&< 4.0.1	4.0.1`composer require moodle/moodle:^4.0.1`
🐘Packagist	`moodle/moodle`	≥ 3.9&&< 3.9.14	3.9.14`composer require moodle/moodle:^3.9.14`
🐘Packagist	`moodle/moodle`	≥ 3.10&&< 3.10.11	3.10.11`composer require moodle/moodle:^3.10.11`
🐘Packagist	`moodle/moodle`	≥ 3.11&&< 3.11.7	3.11.7`composer require moodle/moodle:^3.11.7`

Affected Products

3 products · 8 configurations

fedorafedoraproject

3 versions

343536

Application

moodlemoodle

≥ 3.11 && < 3.11.7

1 version

4.0.0

enterprise linuxredhat

1 version

8.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A flaw was found in moodle where logic used to count failed login attemp…

github.comGithubOct 2022

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.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30600 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

A flaw was found in moodle where logic used to count failed login attempts could result in the account lockout threshold being bypassed.

O3 Security · Impact-Aware SCA

Is CVE-2022-30600 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works