How severe is CVE-2022-30599?

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

Which packages are affected by CVE-2022-30599?

CVE-2022-30599 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-30599?

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-30599 is resolved across your whole dependency graph.

How do I detect CVE-2022-30599 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-30599 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2022-30599 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-30599 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-2022-30599?

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

CVE-2022-30599 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2022-30599 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-30599 — moodle

CRITICALFix: moodle/moodle@a0f47c8

CVE-2022-30599 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.

SQL injection in moodle

Also known asBIT-moodle-2022-30599GHSA-69c3-5xxf-58q2

Published

May 18, 2022

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% 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 an SQL injection risk was identified in Badges code relating to configuring criteria.

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.11&&< 3.11.7	3.11.7`composer require moodle/moodle:^3.11.7`
🐘Packagist	`moodle/moodle`	≥ 3.10&&< 3.10.11	3.10.11`composer require moodle/moodle:^3.10.11`
🐘Packagist	`moodle/moodle`	≥ 3.9&&< 3.9.14	3.9.14`composer require moodle/moodle:^3.9.14`

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

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-30599 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

A flaw was found in moodle where an SQL injection risk was identified in Badges code relating to configuring criteria.

O3 Security · Impact-Aware SCA

Is CVE-2022-30599 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works