GHSA-r6h7-846c-8m78 — elgg/elgg
MEDIUMGHSA-r6h7-846c-8m78 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in elgg/elgg. A fix is available for elgg/elgg — see the affected versions and patch details below.
Elgg open redirect
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-r6h7-846c-8m78 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
elgg/elgg🐘elgg/elggReal-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
Elgg before 1.12.18 and 2.3.x before 2.3.11 has an open redirect.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | elgg/elgg | all versions | 1.12.18composer require elgg/elgg:^1.12.18 |
| 🐘Packagist | elgg/elgg | ≥ 2.3.0&&< 2.3.11 | 2.3.11composer require elgg/elgg:^2.3.11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for elgg/elgg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update elgg/elgg to 1.12.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6h7-846c-8m78 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r6h7-846c-8m78 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r6h7-846c-8m78. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-r6h7-846c-8m78 in your dependencies?
O3 Security finds GHSA-r6h7-846c-8m78 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.