How severe is GHSA-79mg-4w23-4fqc?

GHSA-79mg-4w23-4fqc has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-79mg-4w23-4fqc?

GHSA-79mg-4w23-4fqc affects the following packages: cachethq/cachet (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-79mg-4w23-4fqc?

No patched version of cachethq/cachet has shipped for GHSA-79mg-4w23-4fqc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-79mg-4w23-4fqc in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cachethq/cachet. 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-79mg-4w23-4fqc 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-79mg-4w23-4fqc?

O3 pinpoints whether GHSA-79mg-4w23-4fqc 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-79mg-4w23-4fqc actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-79mg-4w23-4fqc, including 1 in-the-wild exploitation observed on GitHub and other sources. 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-79mg-4w23-4fqc?

GHSA-79mg-4w23-4fqc has an EPSS (Exploit Prediction Scoring System) score of 9.8%, placing it in the 95th 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-79mg-4w23-4fqc?

GHSA-79mg-4w23-4fqc is classified as SQL Injection (CWE-89), Improper Authentication (CWE-287). These weakness types 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.

Is there exploit tooling available for GHSA-79mg-4w23-4fqc?

A Nuclei detection template exists for GHSA-79mg-4w23-4fqc, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-79mg-4w23-4fqc published, and has it been updated?

GHSA-79mg-4w23-4fqc was published on August 30, 2021 and was last updated on March 13, 2026. 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-79mg-4w23-4fqc

HIGH

Unauthenticated SQL Injection in Cachet

Also known asCVE-2021-39165

Published

Aug 30, 2021

Updated

Mar 13, 2026

Affected

1 pkg

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

9.8%probability of exploitation in next 30 days

Lower Risk95th percentile-79.62%

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

🐘cachethq/cachet

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

Impact

In Cachet versions through 2.3.18, there is a SQL injection which is in the SearchableTrait#scopeSearch(). Attackers without authentication can utilize this vulnerability to exfiltrate sensitive data from the database such as administrator's password and session.

Patches

The original repository of https://github.com/CachetHQ/Cachet is not active, the stable version 2.3.18 and it's developing 2.4 branch is affected.

Update to version 2.5 or later in the https://github.com/fiveai/Cachet fork to fix this vulnerability.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`cachethq/cachet`	all versions	No fix

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.

Cachet is an open source status page. With Cachet prior to and including…

github.comGithubMar 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cachethq/cachet. 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.
Remediation status
No patched version of cachethq/cachet has shipped for GHSA-79mg-4w23-4fqc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-79mg-4w23-4fqc 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-79mg-4w23-4fqc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact In Cachet versions through 2.3.18, there is a SQL injection which is in the `SearchableTrait#scopeSearch()`. Attackers without authentication can utilize this vulnerability to exfiltrate sensitive data from the database such as administrator's password and session. ### Patches The original repository of [https://github.com/CachetHQ/Cachet](https://github.com/CachetHQ/Cachet) is not active, the stable version 2.3.18 and it's developing 2.4 branch is affected. Update to version 2.5 or later in the [https://github.com/fiveai/Cachet fork](https://github.com/fiveai/Cachet) to fix thi

O3 Security · Impact-Aware SCA

Is GHSA-79mg-4w23-4fqc in your dependencies?

O3 detects GHSA-79mg-4w23-4fqc 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