CVE-2024-26470 — FullStackHero.WebAPI.Boil…
HIGHCVE-2024-26470 is a high-severity (CVSS 8.1) Information Exposure vulnerability in FullStackHero.WebAPI.Boilerplate. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
FullStackHero's WebAPI Boilerplate host header injection vulnerability
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-26470.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
FullStackHero.WebAPI.BoilerplateReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
A host header injection vulnerability in the forgot password function of FullStackHero's WebAPI Boilerplate v1.0.0 and v1.0.1 allows attackers to leak the password reset token via a crafted request.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | FullStackHero.WebAPI.Boilerplate | ≥ 1.0.0 | No fix |
Affected Products
.net 9 starter kitfullstackheroDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for FullStackHero.WebAPI.Boilerplate, 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 FullStackHero.WebAPI.Boilerplate for CVE-2024-26470. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2024-26470 in your dependencies?
Find it across NuGet, including transitive dependencies.