How severe is GHSA-phg7-8mm9-gj88?

GHSA-phg7-8mm9-gj88 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-phg7-8mm9-gj88?

GHSA-phg7-8mm9-gj88 affects the following packages: egroupware/egroupware (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-phg7-8mm9-gj88?

Update egroupware/egroupware to 23.1.20240624 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-phg7-8mm9-gj88 is resolved across your whole dependency graph.

How do I detect GHSA-phg7-8mm9-gj88 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for egroupware/egroupware. 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-phg7-8mm9-gj88 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-phg7-8mm9-gj88?

O3 pinpoints whether GHSA-phg7-8mm9-gj88 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-phg7-8mm9-gj88 actively exploited in the wild?

No public exploit code has been indexed for GHSA-phg7-8mm9-gj88 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-phg7-8mm9-gj88?

GHSA-phg7-8mm9-gj88 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 47th 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-phg7-8mm9-gj88?

GHSA-phg7-8mm9-gj88 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 GHSA-phg7-8mm9-gj88 published, and has it been updated?

GHSA-phg7-8mm9-gj88 was published on July 7, 2024 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-phg7-8mm9-gj88: EGroupware mishandles an ORDER BY clause…

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk47th percentile+0.53%

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

1 pkg affected

🐘egroupware/egroupware

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

EGroupware before 23.1.20240624 mishandles an ORDER BY clause. This leads to json.php menuaction=EGroupware\Api\Etemplate\Widget\Nextmatch::ajax_get_rows sort.id SQL injection by authenticated users for Address Book or InfoLog sorting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`egroupware/egroupware`	all versions	23.1.20240624

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for egroupware/egroupware. 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 egroupware/egroupware to 23.1.20240624 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-phg7-8mm9-gj88 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-phg7-8mm9-gj88 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-phg7-8mm9-gj88. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

EGroupware before 23.1.20240624 mishandles an ORDER BY clause. This leads to json.php menuaction=EGroupware\Api\Etemplate\Widget\Nextmatch::ajax_get_rows sort.id SQL injection by authenticated users for Address Book or InfoLog sorting.

O3 Security · Impact-Aware SCA

Is GHSA-phg7-8mm9-gj88 in your dependencies?

O3 detects GHSA-phg7-8mm9-gj88 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

GHSA-phg7-8mm9-gj88