CVE-2005-1956
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 · uneditedFile Upload Manager allows remote attackers to upload arbitrary files by modifying the test variable to contain a value of '~~~~~~' (six tildes), which bypasses the file extension checks.
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 confidenceThe File Upload Manager application has a logic flaw in its file extension validation. Attackers can bypass extension checks by setting a 'test' variable to '~~~~~~' (six tildes), which causes the validation logic to fail to properly check the uploaded file's extension. This allows remote attackers to upload arbitrary file types including potentially malicious executables.
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 dataall versionsCVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Locate the File Upload Manager applicationSearch for the File Upload Manager web application in your environment - check for upload-handling scripts, forms, or components that handle file uploadsAffected if File Upload Manager is present in the environment
-
Identify file upload functionalityFind the file upload endpoint and examine how file uploads are handled - look for the form or API that accepts file submissionsAffected if File upload functionality exists and is accessible
-
Test extension validation bypass with test parameterSubmit a file upload request with the 'test' parameter set to '~~~~~~' (six tildes) and observe whether extension validation is properly enforcedAffected if The uploaded file passes extension validation when test=~~~~~~ is provided but would fail without this parameter value
-
Verify arbitrary file type upload is possibleAttempt to upload files with non-standard or executable extensions (such as .exe, .php, .asp, .jsp) using the test parameter bypassAffected if Files with dangerous or unexpected extensions can be successfully uploaded
The environment is affected if File Upload Manager is present and setting test=~~~~~~ allows uploading files with extensions that should be blocked by validation logic
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 file extension validation logic to properly validate file types regardless of the 'test' variable value. Implement server-side validation that checks actual file content/magic bytes rather than relying solely on file extensions or client-controllable parameters.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1956 — 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-2005-1956 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