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

CVE-2022-0814 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: 9.5%.

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

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

Ubigeo De Peru Para Woocommerce CVE-2022-0814

CRITICAL

SQL Injection (CWE-89)

2022-05-09 contact@wpscan.com

SQLi WordPress Ubigeo De Peru Para Woocommerce

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

May 09, 2022 - 17:15 nvd

CRITICAL 9.8

DescriptionNVD

AnalysisAI

The Ubigeo de Perú para Woocommerce WordPress plugin before 3.6.4 does not properly sanitise and escape some parameters before using them in SQL statements via various AJAX actions, some of which are. Rated critical severity (CVSS 9.8), 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 SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. The Ubigeo de Perú para Woocommerce WordPress plugin before 3.6.4 does not properly sanitise and escape some parameters before using them in SQL statements via various AJAX actions, some of which are available to unauthenticated users, leading to SQL Injections Affected products include: Ubigeo De Peru Para Woocommerce Project Ubigeo De Peru Para Woocommerce. Version information: before 3.6.4.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.