LiveActive security incident?Get immediate response
CVE Record

CVE-2019-4747: IBM Team Concert (RTC) is vulnerable to cross-site scripting.

IBM Team Concert (RTC) is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 172887.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

IBM Rational Team Concert has a stored cross-site scripting issue in the web interface. An authenticated user could place JavaScript into the UI, potentially changing what another trusted session sees and exposing credentials. This is a moderate business risk, especially where RTC is used by many internal users or contains sensitive engineering data.

Executive priority

Schedule remediation in the normal vulnerability cycle, faster for externally reachable or highly collaborative RTC environments. The main business concern is credential exposure or workflow manipulation inside a trusted engineering session, not full server takeover based on the provided evidence.

Technical view

CVE-2019-4747 affects IBM Rational Team Concert versions 6.0.2, 6.0.6, 6.0.6.1, and 7.0. The issue is web UI XSS requiring network access, low privileges, and user interaction. CVSS 3.0 score is 5.4 with changed scope and low confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to organizations running affected IBM RTC versions with accessible web UI. Risk increases where many authenticated users can create or edit content viewed by others, or where RTC sessions have access to sensitive project data.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates user interaction and low privileges are required. Treat it as credible XSS risk, not as confirmed in-the-wild exploitation.

Researcher notes

Evidence identifies XSS in IBM RTC Web UI with affected versions and CVSS details, but does not provide the exact vulnerable field, endpoint, patch level, or exploit pattern. Avoid assuming broader IBM Engineering Lifecycle Management impact unless confirmed by IBM guidance.

Mitigation direction

  • Identify RTC instances running versions 6.0.2, 6.0.6, 6.0.6.1, or 7.0.
  • Review IBM advisory for fixed levels or official workaround details.
  • Restrict RTC Web UI access to trusted networks and authenticated users.
  • Reduce content-editing permissions where broad write access is unnecessary.
  • Prioritize remediation for internet-facing or partner-accessible RTC deployments.

Validation and detection

  • Inventory deployed IBM Rational Team Concert versions.
  • Check IBM advisory against current build and patch level.
  • Review RTC roles that can create or modify web-visible content.
  • Inspect security logs for suspicious script-like content in RTC records.
  • Confirm remediation in a test environment before production rollout.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-4747 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/UI:R/PR:L/C:L/A:N/S:C/AC:L/I:L/RC:C/RL:O/E:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.0MediumCVSS:3.0/AV:N/UI:R/PR:L/C:L/A:N/S:C/AC:L/I:L/RC:C/RL:O/E:H2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.4Medium
CVSS 3.0 vector shape for CVE-2019-4747Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/UI:R/PR:L/C:L/A:N/S:C/AC:L/I:L/RC:C/RL:O/E:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMRational Team Concert6.0.2, 6.0.6, 6.0.6.1, 7.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.