GHSA-9jxw-cfrh-jxq6
HIGHGHSA-9jxw-cfrh-jxq6 is a high-severity (CVSS 8.8) CWE-93 vulnerability in cachethq/cachet. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-9jxw-cfrh-jxq6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cachet vulnerable to new line injection during configuration edition
Blast Radius
cachethq/cachetReal-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
Authenticated users, regardless of their privileges (User or Admin), can exploit a new line injection in the configuration edition feature (e.g. mail settings) and gain arbitrary code execution on the server.
Patches
This issue was addressed by improving UpdateConfigCommandHandler and preventing the use of new lines characters in new configuration values.
Workarounds
Only allow trusted source IP addresses to access to the administration dashboard.
References
For more information
If you have any questions or comments about this advisory, you can contact:
- The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
- The maintainers, by opening an issue on this repository.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | cachethq/cachet | all versions | 2.5.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update cachethq/cachet to 2.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jxw-cfrh-jxq6 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-9jxw-cfrh-jxq6 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-9jxw-cfrh-jxq6. 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-9jxw-cfrh-jxq6 in your dependencies?
O3 detects GHSA-9jxw-cfrh-jxq6 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.