How severe is GHSA-qqjv-mc2v-p7mc?

GHSA-qqjv-mc2v-p7mc has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qqjv-mc2v-p7mc?

GHSA-qqjv-mc2v-p7mc affects the following packages: moodle/moodle (Packagist), moodle/moodle (Packagist), moodle/moodle (Packagist), moodle/moodle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qqjv-mc2v-p7mc?

Update moodle/moodle to 3.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqjv-mc2v-p7mc is resolved across your whole dependency graph.

How do I detect GHSA-qqjv-mc2v-p7mc in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moodle/moodle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qqjv-mc2v-p7mc 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.

How does O3 Security protect against GHSA-qqjv-mc2v-p7mc?

O3 pinpoints whether GHSA-qqjv-mc2v-p7mc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qqjv-mc2v-p7mc actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-qqjv-mc2v-p7mc, including 1 documented proof-of-concept exploit on Exploit-DB. 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 GHSA-qqjv-mc2v-p7mc?

GHSA-qqjv-mc2v-p7mc has an EPSS (Exploit Prediction Scoring System) score of 15.9%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-qqjv-mc2v-p7mc?

GHSA-qqjv-mc2v-p7mc is classified as Server-Side Request Forgery (SSRF) (CWE-918). 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 GHSA-qqjv-mc2v-p7mc published, and has it been updated?

GHSA-qqjv-mc2v-p7mc was published on May 14, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-qqjv-mc2v-p7mc

MEDIUM

Moodle SSRF Vulnerability

Also known asCVE-2018-1042

Published

May 14, 2022

Updated

Feb 16, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

15.9%probability of exploitation in next 30 days

Moderate Risk96th percentile+2.99%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

Moodle 3.x has Server Side Request Forgery in the filepicker.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	≥ 3.4&&< 3.4.1	3.4.1
🐘Packagist	`moodle/moodle`	≥ 3.3&&< 3.3.4	3.3.4
🐘Packagist	`moodle/moodle`	≥ 3.2&&< 3.2.7	3.2.7
🐘Packagist	`moodle/moodle`	≥ 3.1&&< 3.1.10	3.1.10

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.

EDB-47177webappsphp

Moodle Filepicker 3.5.2 - Server Side Request Forgery

by Fabian Mosch_ Nick Theisinger · Jul 26, 2019

Exploit-DB Source

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update moodle/moodle to 3.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqjv-mc2v-p7mc 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.
How O3 protects you
O3 pinpoints whether GHSA-qqjv-mc2v-p7mc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qqjv-mc2v-p7mc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Moodle 3.x has Server Side Request Forgery in the filepicker.

O3 Security · Impact-Aware SCA

Is GHSA-qqjv-mc2v-p7mc in your dependencies?

O3 detects GHSA-qqjv-mc2v-p7mc across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works