dbcve.org
Open RedirectWeakness · CWE-601

CVE-2025-62428

HIGH · 8.8 CVSS v4.0 Published 2025-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Drawing-Captcha APP provides interactive, engaging verification for Web-Based Applications. The vulnerability is a Host Header Injection in the /register and /confirm-email endpoints. It allows an attacker to manipulate the Host header in HTTP requests to generate malicious email confirmation links. These links can redirect users to attacker-controlled domains. This vulnerability affects all users relying on email confirmation for account registration or verification. This vulnerability is fixed in 1.2.5-alpha-patch.

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 confidence

Host Header Injection in Drawing-Captcha APP allows attackers to manipulate the Host header in HTTP requests to /register and /confirm-email endpoints. The application uses this header value when generating email confirmation links, causing links to point to attacker-controlled domains instead of legitimate ones, enabling credential theft or malware distribution when users click malicious links.

MitigationUpgrade to version 1.2.5-alpha-patch immediately. Additionally, implement server-side host header validation/whitelisting to ensure the Host header matches expected values as a defense-in-depth measure.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Drawing-Captcha APP is installed
    Check your web server logs, application directory, or running processes for the Drawing-Captcha application. Look for application files, services, or containers running this specific app.
    Affected if Drawing-Captcha APP is present in your environment
  2. Determine the installed version
    Check the application's version file, package.json, or the application header/version endpoint. Compare your version against any released versions, noting that versions prior to 1.2.5-alpha-patch are affected.
    Affected if The installed version is earlier than 1.2.5-alpha-patch or the version cannot be determined
  3. Verify the vulnerable endpoints are exposed
    Check if the application routing exposes /register and /confirm-email endpoints. Review your web server configuration, reverse proxy rules, or application routing configuration to confirm these paths are accessible.
    Affected if The /register and /confirm-email endpoints are accessible without authentication
  4. Inspect Host header handling in the application
    Review the application source code, specifically the registration and email confirmation handlers, to see if the Host header is directly used when constructing confirmation URLs without validation. Search for code that reads request.getHeader("Host") or equivalent and uses it in URL construction.
    Affected if The application uses the Host header value directly in confirmation link generation without sanitization or whitelist validation

You are affected if Drawing-Captcha APP is running and the /register or /confirm-email endpoints are accessible without proper Host header validation in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.2.5-alpha-patch immediately. Additionally, implement server-side host header validation/whitelisting to ensure the Host header matches expected values as a defense-in-depth measure.

Recommended fix Moderate confidence

1.2.5-alpha-patch

  1. 1. Identify the currently installed version of Drawing-Captcha APP
  2. 2. Download or obtain version 1.2.5-alpha-patch from the official source
  3. 3. Backup the current installation and database
  4. 4. Install version 1.2.5-alpha-patch following the standard upgrade procedure
  5. 5. Verify the fix by testing the /register and /confirm-email endpoints with manipulated Host headers
  6. 6. Confirm that email confirmation links now use the correct, expected domain

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62428 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62428 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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