What is the CVSS score of CVE-2018-3735?

CVE-2018-3735 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.8%.

Is there a public PoC exploit available for CVE-2018-3735?

Yes, a public proof-of-concept exploit is available for CVE-2018-3735. Prioritise patching immediately. EPSS: 0.8%.

Bracket Template CVE-2018-3735

MEDIUM

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

2018-06-07 support@hackerone.com

XSS Bracket Template

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

Jun 07, 2018 - 02:29 nvd

MEDIUM 6.1

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

3 npm packages depend on bracket-template (3 direct, 0 indirect)

Ecosystem-wide dependent count for version 1.1.5.

DescriptionNVD

bracket-template suffers from reflected XSS possible when variable passed via GET parameter is used in template

AnalysisAI

bracket-template suffers from reflected XSS possible when variable passed via GET parameter is used in template. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

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. bracket-template suffers from reflected XSS possible when variable passed via GET parameter is used in template Affected products include: Bracket-Template Project Bracket-Template.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.