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

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

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

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

Is there a patch available for CVE-2019-7173?

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

Croogo CVE-2019-7173

MEDIUM

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

2019-01-29 cve@mitre.org

XSS Croogo

4.8

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

4.8 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Jan 29, 2019 - 18:29 nvd

MEDIUM 4.8

DescriptionNVD

A stored-self XSS exists in Croogo through v3.0.5, allowing an attacker to execute HTML or JavaScript code in a vulnerable Title field to /admin/file-manager/attachments/edit/4.

AnalysisAI

A stored-self XSS exists in Croogo through v3.0.5, allowing an attacker to execute HTML or JavaScript code in a vulnerable Title field to /admin/file-manager/attachments/edit/4. Rated medium severity (CVSS 4.8), this vulnerability is remotely exploitable, 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. A stored-self XSS exists in Croogo through v3.0.5, allowing an attacker to execute HTML or JavaScript code in a vulnerable Title field to /admin/file-manager/attachments/edit/4. Affected products include: Croogo.

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.