CVE-2025-70948
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 mailer component of @perfood/couch-auth v0.26.0 allows attackers to obtain reset tokens and execute an account takeover via spoofing the HTTP Host header.
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 vulnerability in the mailer component of @perfood/couch-auth v0.26.0 allows attackers to spoof the HTTP Host header when requesting password resets, causing reset tokens to be sent to attacker-controlled URLs, enabling account takeover.
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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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.
-
Check installed version of @perfood/couch-authRun 'npm list @perfood/couch-auth' or check your package.json to identify the exact version installedAffected if Version is 0.26.0 or any earlier version where the mailer uses the Host header for reset URLs
-
Verify mailer component is configuredInspect your application configuration files for mailer settings, specifically look for password reset email configurationAffected if Mailer is enabled and configured to send password reset emails
-
Inspect password reset URL construction logicExamine the source code of the mailer component, looking for where reset token URLs are built - search for code that uses the Host header or request.hostname in URL constructionAffected if The code uses the HTTP Host header to construct password reset URLs instead of a hardcoded trusted domain
-
Check environment configuration for trusted domain settingsLook for environment variables or config files that specify a trusted domain for password reset URLs; verify if one exists and is being usedAffected if No trusted domain is configured, or the configuration is being ignored in favor of the client-supplied Host header
You are affected if @perfood/couch-auth version 0.26.0 or earlier is installed AND the mailer component is configured to send password reset emails using the client-supplied Host header to construct reset URLs.
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 dataFix the mailer to use a fixed, configured base URL for password reset links rather than trusting the HTTP Host header, or implement strict Host header validation and allowlisting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70948 — 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-2025-70948 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