CVE-2001-0693
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 · uneditedWebTrends HTTP Server 3.1c and 3.5 allows a remote attacker to view script source code via a filename followed by an encoded space (%20).
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 confidenceWebTrends HTTP Server 3.1c and 3.5 contains an information disclosure vulnerability where remote attackers can view script source code by appending an encoded space (%20) to a filename in an HTTP request. This allows unauthorized access to potentially sensitive source code.
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= 3.1c= 3.5CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 WebTrends HTTP Server is runningCheck for processes named 'webtrends' or 'wt' in running processes, or check if port 80/443 is listening with WebTrends server bannerAffected if WebTrends HTTP Server is actively running and accessible on the network
-
Check installed WebTrends versionReview installation documentation, registry keys, or run 'wtadmin -v' if available, or check program files for WebTrends version informationAffected if Version is 3.1c or 3.5 for Webtrends Enterprise Reporting Server (or Webtrends Enterprise Reporting Server Nt)
-
Test vulnerability with encoded space injectionSend HTTP GET request to the server appending '%20' to known script filenames (e.g., GET /scripts/login.asp%20 HTTP/1.1) and observe if full source code is returnedAffected if Server returns unparsed script source code (with visible ASP code, variables, logic) instead of executing the script or returning a 404 error
-
Verify HTTP server component is exposedConfirm the WebTrends HTTP server is accessible externally or on untrusted networks, not just localhostAffected if HTTP server listens on external interfaces or is reachable from untrusted networks
User is affected if WebTrends Enterprise Reporting Server versions 3.1c or 3.5 are running with the HTTP server enabled and accessible, and the %20 space injection reveals script source code instead of executing or rejecting the request.
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 WebTrends HTTP Server to a patched version. If no update is available, disable or restrict the HTTP server and implement additional access controls until a secure version can be deployed.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0693 — 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-2001-0693 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