What is the CVSS score of CVE-2020-11887?

CVE-2020-11887 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.7%.

Is there a public PoC exploit available for CVE-2020-11887?

Yes, a public proof-of-concept exploit is available for CVE-2020-11887. Prioritise patching immediately. EPSS: 0.7%.

Svg2Png CVE-2020-11887

MEDIUM

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

2020-04-17 cve@mitre.org

XSS SSRF Svg2Png

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 17, 2020 - 21:15 nvd

MEDIUM 6.1

Blast Radius

ecosystem impact

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

149 npm packages depend on svg2png (91 direct, 59 indirect)

Ecosystem-wide dependent count for version 4.1.1.

DescriptionNVD

svg2png 4.1.1 allows XSS with resultant SSRF via JavaScript inside an SVG document.

AnalysisAI

svg2png 4.1.1 allows XSS with resultant SSRF via JavaScript inside an SVG document. 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. svg2png 4.1.1 allows XSS with resultant SSRF via JavaScript inside an SVG document. Affected products include: Svg2Png Project Svg2Png.

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.