How severe is GHSA-g8r3-2v89-j6r5?

No CVSS score has been assigned to GHSA-g8r3-2v89-j6r5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g8r3-2v89-j6r5?

GHSA-g8r3-2v89-j6r5 affects the following packages: moodle/moodle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-g8r3-2v89-j6r5?

Update moodle/moodle to 4.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g8r3-2v89-j6r5 is resolved across your whole dependency graph.

How do I detect GHSA-g8r3-2v89-j6r5 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-g8r3-2v89-j6r5 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-g8r3-2v89-j6r5?

O3 pinpoints whether GHSA-g8r3-2v89-j6r5 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-g8r3-2v89-j6r5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g8r3-2v89-j6r5 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 type of vulnerability is GHSA-g8r3-2v89-j6r5?

GHSA-g8r3-2v89-j6r5 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g8r3-2v89-j6r5 published, and has it been updated?

GHSA-g8r3-2v89-j6r5 was published on November 13, 2024 and was last updated on June 13, 2025. 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

GHSA-g8r3-2v89-j6r5

GHSA-g8r3-2v89-j6r5 is a Information Exposure vulnerability in moodle/moodle. O3 Security confirms whether GHSA-g8r3-2v89-j6r5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Moodle IDOR when accessing list of badge recipients

Also known asBIT-moodle-2024-48900CVE-2024-48900

Published

Nov 13, 2024

Updated

Jun 13, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 13, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘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 vulnerability was found in Moodle. Additional checks are required to ensure users with permission to view badge recipients can only access lists of those they are intended to have access to.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	≥ 4.4.0&&< 4.4.4	4.4.4

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 4.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g8r3-2v89-j6r5 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-g8r3-2v89-j6r5 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-g8r3-2v89-j6r5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability was found in Moodle. Additional checks are required to ensure users with permission to view badge recipients can only access lists of those they are intended to have access to.

O3 Security · Impact-Aware SCA

Is GHSA-g8r3-2v89-j6r5 in your dependencies?

O3 detects GHSA-g8r3-2v89-j6r5 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