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

CVE-2022-0254 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 2.0%.

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

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

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

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

Zero Spam CVE-2022-0254

CRITICAL

SQL Injection (CWE-89)

2022-03-14 contact@wpscan.com

SQLi WordPress Zero Spam

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Mar 14, 2022 - 15:15 nvd

CRITICAL 9.8

DescriptionNVD

AnalysisAI

The WordPress Zero Spam WordPress plugin before 5.2.11 does not properly sanitise and escape the order and orderby parameters before using them in a SQL statement in the admin dashboard, leading to a. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. The WordPress Zero Spam WordPress plugin before 5.2.11 does not properly sanitise and escape the order and orderby parameters before using them in a SQL statement in the admin dashboard, leading to a SQL injection Affected products include: Highfivery Zero-Spam. Version information: before 5.2.11.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.