What is the CVSS score of CVE-2019-9557?

CVE-2019-9557 has a CVSS 3.0 base score of 6.1 (Medium). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 1.0%.

Is there a public PoC exploit available for CVE-2019-9557?

Yes, a public proof-of-concept exploit is available for CVE-2019-9557. Prioritise patching immediately. EPSS: 1.0%.

Ability Mail Server CVE-2019-9557

MEDIUM

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

2019-03-12 cve@mitre.org

XSS Ability Mail Server

6.1

CVSS 3.0 · 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.0/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

Mar 12, 2019 - 19:29 nvd

MEDIUM 6.1

DescriptionNVD

Ability Mail Server 4.2.6 has Persistent Cross Site Scripting (XSS) via the body e-mail body. To exploit the vulnerability, the victim must open an email with malicious Javascript inserted into the body of the email as an iframe.

AnalysisAI

Ability Mail Server 4.2.6 has Persistent Cross Site Scripting (XSS) via the body e-mail body. 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. Ability Mail Server 4.2.6 has Persistent Cross Site Scripting (XSS) via the body e-mail body. To exploit the vulnerability, the victim must open an email with malicious Javascript inserted into the body of the email as an iframe. Affected products include: Codecrafters Ability Mail Server.

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.