CVE-2024-1893

Easy Property Listings <= 3.5.2 - Authenticated(Contributor+) SQL Injection via Shortcode

2024-03-21 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 3.5.3
Affected Plugin
Easy Property Listings
Affected Version
<= 3.5.2
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2024-1893
View all Easy Property Listings vulnerabilities

At a glance

CVE-2024-1893 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Easy Property Listings WordPress plugin, affecting versions <= 3.5.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.5.3; sites on affected versions should update now. Disclosed March 2024, reported by Krzysztof Zając.

Vulnerability Overview

The Easy Property Listings plugin for WordPress is vulnerable to time-based SQL Injection via the ‘property_status’ shortcode attribute in all versions up to, and including, 3.5.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor access and above, 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 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')

Easy Property Listings <= 3.5.2 carries this weakness at property_status, and reaching it takes an account at Contributor level or above. 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 Easy Property Listings the fix is 3.5.3: builds <= 3.5.2 are affected, anything from 3.5.3 onward is not.

Remediation

Update to version 3.5.3, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Easy Property Listings 3.5.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-1893https://www.wordfence.com/threat-intel/vulnerabilities/id/a7ac96db-2d9a-4eaf-8916-a02e3e64ca4ahttps://nvd.nist.gov/vuln/detail/CVE-2024-1893

Related records

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