dbcve.org
ConnectionsApplication · Ibm

CVE-2015-5035

MEDIUM · 5.4 CVSS v3.0 Published 2016-01-03
Fix available
A fix is available. Upgrade to after 3.0.1.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Cross-site scripting (XSS) vulnerability in IBM Connections 3.x before 3.0.1.1 CR3, 4.0 before CR4, 4.5 before CR5, and 5.0 before CR3 allows remote authenticated users to inject arbitrary web script or HTML via a crafted URL, a different vulnerability than CVE-2015-5036.

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 confidence

Cross-site scripting (XSS) vulnerability in IBM Connections allows authenticated users to inject arbitrary web script or HTML via a crafted URL. The vulnerability affects versions 3.x before 3.0.1.1 CR3, 4.0 before CR4, 4.5 before CR5, and 5.0 before CR3.

MitigationUpgrade IBM Connections to the specified critical release versions (3.0.1.1 CR3, 4.0 CR4, 4.5 CR5, or 5.0 CR3) to address the XSS vulnerability.

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
ConnectionsApplication
Affected:<= 3.0.1.1= 4.0= 4.5= 5.0

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Connections version
    Log into the IBM Connections Administration Dashboard or check the version file in the IBM Connections installation directory (typically found in the version.txt or about.html file in the connections root directory)
    Affected if The installed version is 3.x before 3.0.1.1 CR3, 4.0 before CR4, 4.5 before CR5, 5.0 before CR3, or any version <= 3.0.1.1, 4.0, 4.5, or 5.0 without the Critical Release fixes
  2. Verify the Critical Release patch level
    Check the IBM Connections installed via the IBM Fix Central or examine the detailed version information in the IBM Connections Admin Console under 'System Diagnostics' or 'About IBM Connections'
    Affected if The version shows as 3.0.1.1 without CR3, 4.0 without CR4, 4.5 without CR5, or 5.0 without CR3 applied

You are affected if your IBM Connections installation is any version before 3.0.1.1 CR3, 4.0 CR4, 4.5 CR5, or 5.0 CR3 without the critical release patches applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.0.1.1
Interim mitigation

Upgrade IBM Connections to the specified critical release versions (3.0.1.1 CR3, 4.0 CR4, 4.5 CR5, or 5.0 CR3) to address the XSS vulnerability.

Fix this in Connections Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-5035 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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