CVE-2018-18288
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 · uneditedCrushFTP through 8.3.0 is vulnerable to credentials theft via URL redirection.
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 · moderate confidenceCrushFTP through version 8.3.0 contains a URL redirection vulnerability that allows attackers to craft malicious URLs redirecting users to attacker-controlled sites. This open redirect can be leveraged in phishing attacks to steal user credentials by tricking users into entering credentials on a lookalike login page hosted on the redirected domain.
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<= 8.3.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.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 installed CrushFTP versionAccess the CrushFTP admin interface or check the application files for the version number. Common locations include the admin login page or the installation directory version file.Affected if The installed version is CrushFTP 8.3.0 or any earlier version.
-
Verify web interface accessibilityConfirm that the CrushFTP web interface (typically on ports 8080 or 8443) is accessible from network locations that could be targeted by attackers.Affected if The web interface is exposed externally or to untrusted networks without additional access controls.
-
Test for open redirect behaviorCraft a test URL using the CrushFTP web interface with a redirect parameter pointing to an external domain (for example: https://your-crushftp-server/;http://example.com). Observe whether the application redirects to the external domain.Affected if The application redirects to arbitrary external domains specified in the URL parameters without validating the target domain.
You are affected if your installed CrushFTP version is 8.3.0 or earlier and the web interface redirect functionality allows navigation to external, unvalidated domains.
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 CrushFTP to a version newer than 8.3.0 or apply the vendor-supplied patch. Additionally, implement URL allowlist validation for any redirect functionality to prevent unauthorized domain redirects.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18288 — 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-2018-18288 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