What is the CVSS score of CVE-2016-5682?

CVE-2016-5682 has a CVSS 3.1 base score of 6.1 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.3%.

Is there a public PoC exploit available for CVE-2016-5682?

Yes, a public proof-of-concept exploit is available for CVE-2016-5682. Prioritise patching immediately. EPSS: 0.3%.

Is there a patch available for CVE-2016-5682?

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

Swagger Ui CVE-2016-5682

MEDIUM

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

2017-04-10 cret@cert.org

XSS Swagger Ui

6.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.1 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Apr 10, 2017 - 03:59 cve.org

MEDIUM 6.1

DescriptionCVE.org

Swagger-UI before 2.2.1 has XSS via the Default field in the Definitions section.

AnalysisAI

Swagger-UI before 2.2.1 has XSS via the Default field in the Definitions section. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Cross-Site Scripting (XSS) vulnerability could allow attackers to inject malicious scripts into web pages viewed by other users.

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. Swagger-UI before 2.2.1 has XSS via the Default field in the Definitions section. Affected products include: Smartbear Swagger-Ui. Version information: before 2.2.1.

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.