CVE-2015-0126
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 · uneditedIBM Leads 7.x, 8.1.0 before 8.1.0.14, 8.2, 8.5.0 before 8.5.0.7.3, 8.6.0 before 8.6.0.8.1, 9.0.0 through 9.0.0.4, 9.1.0 before 9.1.0.6.1, and 9.1.1 before 9.1.1.0.2 allows remote authenticated users to bypass intended file-upload restrictions via a modified extension.
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 confidenceIBM Leads contains a file upload validation flaw where authenticated users can bypass intended file extension restrictions by modifying the file extension during upload. This allows uploading of files with potentially dangerous extensions that should be blocked by the application's security controls.
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= 7.1.0= 7.1.1= 7.5.0= 8.1.0= 8.2.0= 8.5.0= 8.6.0= 9.0.0= 9.1.0= 9.1.1CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 IBM Leads installed versionCheck the IBM Leads installation directory for version information, or access the IBM Leads about page through the web interface (typically under Help > About or /leads/index.jsp?command=about). Look for the exact version number in the format like 7.1.0, 8.5.0, 9.1.1, etc.Affected if The installed version matches any of these: 7.1.0, 7.1.1, 7.5.0, 8.1.0, 8.2.0, 8.5.0, 8.6.0, 9.0.0, 9.1.0, or 9.1.1 (or any version lower than the patched versions: 8.1.0.14, 8.5.0.7.3, 8.6.0.8.1, 9.0.0.5, 9.1.0.6.1, 9.1.1.0.2)
-
Confirm file upload feature is accessibleLog in to IBM Leads as an authenticated user and navigate to the file upload functionality. This is typically found in document management, lead attachment, or content management sections where users can upload files to leads or records.Affected if The file upload feature is available and accessible to authenticated users in the IBM Leads application
-
Review file extension validation configurationInspect the IBM Leads configuration files for file upload restrictions. Check web.xml, upload configuration files, or security settings in the IBM Leads installation directory for file extension whitelist/blacklist configurations.Affected if The file extension validation can be bypassed by modifying file extensions during upload, or if no server-side file type validation is configured
You are affected if your IBM Leads version is one of the listed affected versions AND the file upload feature is accessible to authenticated users without proper server-side validation.
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 dataApply the vendor patches: upgrade to 8.1.0.14, 8.5.0.7.3, 8.6.0.8.1, 9.0.0.5, 9.1.0.6.1, 9.1.1.0.2 or later versions. Additionally, implement server-side file type validation and restrict upload directories to prevent execution.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0126 — 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-2015-0126 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