LaravelFramework / library
CVE-2017-9303
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 · uneditedLaravel 5.4.x before 5.4.22 does not properly constrain the host portion of a password-reset URL, which makes it easier for remote attackers to conduct phishing attacks by specifying an attacker-controlled host.
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 confidenceLaravel 5.4.x before 5.4.22 contains a Host Header Injection vulnerability in the password reset functionality. The framework does not properly validate or constrain the host portion of the password-reset URL, allowing attackers to specify arbitrary attacker-controlled hosts in reset links for phishing campaigns.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LaravelFramework / library
= 5.4.0CVSS 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.0/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 installed Laravel versionCheck the Laravel version in your composer.json file or run 'php artisan --version' in your application rootAffected if The installed version is 5.4.0 through 5.4.21 (versions before 5.4.22)
-
Verify password reset routes are enabledInspect your routes/web.php or routes/api.php for password reset related routes such as 'password.reset' or routes using the Password::routes() methodAffected if Password reset routes are defined and active in your application
-
Confirm password reset functionality is in useCheck if your application uses Laravel's built-in PasswordBroker (typically in app/Http/Controllers/Auth/ForgotPasswordController.php and ResetPasswordController.php)Affected if Your application uses Laravel's default password reset controllers or the Password facade for reset functionality
-
Inspect host validation configurationCheck config/app.php for any 'url' or 'domain' configuration settings. In Laravel 5.4.x, review if the application sets a specific domain for password reset URLs or uses App::guessDomainName()Affected if No explicit domain or URL configuration is set for password reset URLs, allowing the Host header to determine the reset link domain
Your environment is affected if you are running Laravel version 5.4.0 through 5.4.21 and your application has the default password reset functionality enabled with no custom host/domain constraints configured for password 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 dataUpgrade to Laravel 5.4.22 or later which implements proper host validation in password reset URLs. Review application configuration to ensure hostname constraints are enforced.
Fix this in Laravel
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9303 — 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-2017-9303 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