CVE-2024-46452
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Host Header injection vulnerability in the password reset function of VigyBag Open Source Online Shop commit 3f0e21b allows attackers to redirect victim users to a malicious site via a crafted URL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHost Header injection in VigyBag's password reset function allows attackers to control the domain used in reset URLs. The application uses the incoming Host header to construct password reset links sent to users, without proper validation. Attackers can send crafted requests with a malicious Host header, causing legitimate users to receive password reset emails containing attacker-controlled links.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if VigyBag application is deployedReview your web server and application inventory to confirm VigyBag is running. Check application directories, containers, or services for VigyBag-related processes or deployments.Affected if VigyBag is not present in your environment, you are not affected by this CVE.
-
Confirm password reset functionality is enabledLocate the password reset or forgot password endpoint in the application. This is typically accessible via a login page link or direct URL path such as /forgot-password, /reset-password, or /password/reset. Verify the endpoint responds and is accessible.Affected if Password reset functionality is disabled or not present, this specific attack vector does not apply.
-
Inspect password reset code for Host header usageReview the source code or configuration of the password reset handler. Search for code that extracts the Host header value (such as request.getHeader("Host") or similar) and uses it to construct reset URLs. Examine email template or notification logic that generates the reset link.Affected if The application uses the incoming Host header to build reset URLs without validation, your environment is vulnerable to this CVE.
-
Check for Host header validation in reset flowExamine the application code or web server configuration for any allowlist or validation logic that restricts acceptable Host header values. Look for domain validation routines that reject unexpected domains before constructing reset links.Affected if No Host header validation exists, or the validation can be bypassed, the application is affected by this vulnerability.
-
Verify reset link domain in test emailIf possible, trigger a test password reset and examine the generated reset URL in the email or response. Compare the domain portion of the link to your legitimate domain. An attacker-controlled domain indicates exploitation.Affected if Reset URLs contain unexpected or attacker-controlled domains, the vulnerability has been exploited.
Your environment is affected by CVE-2024-46452 if VigyBag is deployed with password reset functionality enabled, and the application constructs reset URLs using the unvalidated incoming Host header value.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict Host header validation using an allowlist of permitted domains, or configure the application to use a fixed domain value for all password reset links rather than trusting user-supplied input.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46452 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46452 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data