How severe is GHSA-847x-x4jg-6gf4?

No CVSS score has been assigned to GHSA-847x-x4jg-6gf4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-847x-x4jg-6gf4?

GHSA-847x-x4jg-6gf4 affects the following packages: croogo/croogo (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-847x-x4jg-6gf4?

The records we use list no patched version of croogo/croogo for GHSA-847x-x4jg-6gf4. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-847x-x4jg-6gf4 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for croogo/croogo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-847x-x4jg-6gf4 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-847x-x4jg-6gf4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-847x-x4jg-6gf4 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-847x-x4jg-6gf4?

GHSA-847x-x4jg-6gf4 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th 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-847x-x4jg-6gf4?

GHSA-847x-x4jg-6gf4 is classified as CWE-444 (CWE-444). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-847x-x4jg-6gf4 published, and has it been updated?

GHSA-847x-x4jg-6gf4 was published on April 21, 2025 and was last updated on April 23, 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

croogo Host header injectionGHSA-847x-x4jg-6gf4

GHSA-847x-x4jg-6gf4 is a CWE-444 vulnerability in croogo/croogo. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2024-29643

Published

Apr 21, 2025

Updated

Apr 23, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-847x-x4jg-6gf4.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘croogo/croogo

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

An issue in croogo v.3.0.2 allows an attacker to perform Host header injection via the feed.rss component.

Affected Packages

1 total

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

Affected Products

1 product · 1 configurations

Application

croogocroogo

1 version

3.0.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for croogo/croogo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of croogo/croogo for GHSA-847x-x4jg-6gf4. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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.

Frequently Asked Questions

An issue in croogo v.3.0.2 allows an attacker to perform Host header injection via the feed.rss component.

O3 Security · Impact-Aware SCA

Is GHSA-847x-x4jg-6gf4 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works