What is the CVSS score of CVE-2015-1910?

CVE-2015-1910 has a CVSS 2.0 base score of 3.5 (Low). CVSS vector: AV:N/AC:M/Au:S/C:N/I:P/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2015-1910?

Yes, a patch is available for CVE-2015-1910. Update the affected software to the latest version immediately.

Infosphere Master Data Management Server CVE-2015-1910

LOW

Cross-site Scripting (XSS) (CWE-79)

2015-05-25 psirt@us.ibm.com

IBM XSS Infosphere Master Data Management Server

3.5

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

3.5 LOW

AV:N/AC:M/Au:S/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:S/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

May 25, 2015 - 00:59 cve.org

LOW 3.5

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in the Reference Data Management component in the server in IBM InfoSphere Master Data Management (MDM) 10.1 before IF1, 11.0 before FP3, and 11.3 allows remote authenticated users to inject arbitrary web script or HTML via a crafted URL.

AnalysisAI

Cross-site scripting (XSS) vulnerability in the Reference Data Management component in the server in IBM InfoSphere Master Data Management (MDM) 10.1 before IF1, 11.0 before FP3, and 11.3 allows. Rated low severity (CVSS 3.5), this vulnerability is remotely exploitable.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Cross-site scripting (XSS) vulnerability in the Reference Data Management component in the server in IBM InfoSphere Master Data Management (MDM) 10.1 before IF1, 11.0 before FP3, and 11.3 allows remote authenticated users to inject arbitrary web script or HTML via a crafted URL. Affected products include: Ibm Infosphere Master Data Management Server.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.