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

CVE-2022-0422 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: 8.1%.

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

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

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

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

White Label Cms CVE-2022-0422

MEDIUM

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

2022-03-07 contact@wpscan.com

XSS WordPress White Label Cms

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

Mar 07, 2022 - 09:15 nvd

MEDIUM 6.1

DescriptionNVD

AnalysisAI

The White Label CMS WordPress plugin before 2.2.9 does not sanitise and validate the wlcms[_login_custom_js] parameter before outputting it back in the response while previewing, leading to a. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, 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. The White Label CMS WordPress plugin before 2.2.9 does not sanitise and validate the wlcms[_login_custom_js] parameter before outputting it back in the response while previewing, leading to a Reflected Cross-Site Scripting issue Affected products include: Videousermanuals White Label Cms. Version information: before 2.2.9.

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.