What is the CVSS score of CVE-2022-2829?

CVE-2022-2829 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.7%.

Is there a public PoC exploit available for CVE-2022-2829?

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

Is there a patch available for CVE-2022-2829?

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

Yetiforce Customer Relationship Management CVE-2022-2829

MEDIUM

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

2022-08-23 security@huntr.dev

XSS Yetiforce Customer Relationship Management

5.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

AV:N/AC:L/PR:L/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:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Aug 23, 2022 - 04:15 nvd

MEDIUM 5.4

DescriptionNVD

Cross-site Scripting (XSS) - Stored in GitHub repository yetiforcecompany/yetiforcecrm prior to 6.4.0.

AnalysisAI

Cross-site Scripting (XSS) - Stored in GitHub repository yetiforcecompany/yetiforcecrm prior to 6.4.0. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code 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. Cross-site Scripting (XSS) - Stored in GitHub repository yetiforcecompany/yetiforcecrm prior to 6.4.0. Affected products include: Yetiforce Yetiforce Customer Relationship Management. Version information: prior to 6.4.0..

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.