CVE-2021-24130

WP Google Map Plugin <= 4.1.4 - Authenticated SQL Injection via Orderby

2020-11-25 00:00
Nguyen Anh Tien

Strategic Overview

Status
Patched in 4.1.5
Affected Version
<= 4.1.4
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24130
View all WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters vulnerabilities

At a glance

CVE-2021-24130 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Maps WordPress plugin, affecting versions <= 4.1.4. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 4.1.5; sites on affected versions should update now. Disclosed November 2020, reported by Nguyen Anh Tien.

Vulnerability Overview

Unvalidated input in the WP Google Map Plugin WordPress plugin, versions before 4.1.5, in the Manage Locations page within the plugin settings was vulnerable to SQL Injection through a high privileged user (admin+).

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 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 WP Maps <= 4.1.4 takes any authenticated account. 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 WP Maps the fix is 4.1.5: builds <= 4.1.4 are affected, anything from 4.1.5 onward is not.

Remediation

Update to version 4.1.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Maps: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Maps 4.1.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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