How severe is GHSA-8g5h-gjwq-w5ch?

No CVSS score has been assigned to GHSA-8g5h-gjwq-w5ch yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8g5h-gjwq-w5ch?

GHSA-8g5h-gjwq-w5ch affects the following packages: moodle/moodle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-8g5h-gjwq-w5ch?

Update moodle/moodle to 4.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8g5h-gjwq-w5ch is resolved across your whole dependency graph.

How do I detect GHSA-8g5h-gjwq-w5ch 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 GHSA-8g5h-gjwq-w5ch 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 GHSA-8g5h-gjwq-w5ch actively exploited in the wild?

No public exploit code has been indexed for GHSA-8g5h-gjwq-w5ch 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 GHSA-8g5h-gjwq-w5ch?

GHSA-8g5h-gjwq-w5ch has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th 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 GHSA-8g5h-gjwq-w5ch?

GHSA-8g5h-gjwq-w5ch is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8g5h-gjwq-w5ch published, and has it been updated?

GHSA-8g5h-gjwq-w5ch was published on May 31, 2024 and was last updated on May 31, 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

Moodle Logout CSRF in admin/tool/mfa/auth.phpGHSA-8g5h-gjwq-w5ch

GHSA-8g5h-gjwq-w5ch is a Cross-Site Request Forgery (CSRF) vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.

Also known asBIT-moodle-2024-34007CVE-2024-34007

Published

May 31, 2024

Updated

May 31, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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 GHSA-8g5h-gjwq-w5ch.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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

The logout option within MFA did not include the necessary token to avoid the risk of users inadvertently being logged out via CSRF.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	≥ 4.3.0&&< 4.3.4	4.3.4`composer require moodle/moodle:^4.3.4`

Affected Products

1 product · 1 configurations

Application

moodlemoodle

≥ 4.3.0 && < 4.3.4

range

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.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8g5h-gjwq-w5ch 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

The logout option within MFA did not include the necessary token to avoid the risk of users inadvertently being logged out via CSRF.

O3 Security · Impact-Aware SCA

Is GHSA-8g5h-gjwq-w5ch in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works