CVE-2022-4681

Hide My WP < 6.2.9 - Unauthenticated SQL Injection

2023-01-11 00:00
Xenofon Vassilakopoulos

Strategic Overview

Status
Patched in 6.2.9
Affected Plugin
Hide My WP - Amazing Security Plugin for WordPress!
Affected Version
< 6.2.9
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2022-4681
View all Hide My WP - Amazing Security Plugin for WordPress! vulnerabilities

At a glance

CVE-2022-4681 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Hide My WP - Amazing Security Plugin for WordPress! WordPress plugin, affecting versions < 6.2.9. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.2.9; sites on affected versions should update now. Disclosed January 2023, reported by Xenofon Vassilakopoulos.

Vulnerability Overview

The Hide My WP plugin for WordPress is vulnerable to SQL Injection via an unknown parameter in versions up to, but not including, 6.2.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Hide My WP - Amazing Security Plugin for WordPress! < 6.2.9 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Hide My WP - Amazing Security Plugin for WordPress! the fix is 6.2.9: builds < 6.2.9 are affected, anything from 6.2.9 onward is not.

Remediation

Update to version 6.2.9, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Hide My WP - Amazing Security Plugin for WordPress! 6.2.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4681https://www.wordfence.com/threat-intel/vulnerabilities/id/396a58d2-8357-4a8b-88a7-8c4917e27eb6https://nvd.nist.gov/vuln/detail/CVE-2022-4681

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C