CVE-2024-12023

FULL – Cliente 3.1.5 - 3.1.25 - Authenticated (Subscriber+) SQL Injection

2025-05-01 00:00
kr0d

Strategic Overview

Status
Patched in 3.1.26
Affected Plugin
FULL – Cliente
Affected Version
<= 3.1.25
CVSS
6.5Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2024-12023
View all FULL – Cliente vulnerabilities

At a glance

CVE-2024-12023 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the FULL WordPress plugin, affecting versions <= 3.1.25. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.1.26; sites on affected versions should update now. Disclosed May 2025, reported by kr0d.

Vulnerability Overview

The FULL – Cliente plugin for WordPress is vulnerable to SQL Injection via the 'formId' parameter in all versions 3.1.5 to 3.1.25 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 Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is only exploitable when the PRO version of the plugin is activated, along with Elementor Pro and Elementor CRM.

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.

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

FULL <= 3.1.25 carries this weakness at formId, and reaching it takes an account at Subscriber 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 FULL the fix is 3.1.26: builds <= 3.1.25 are affected, anything from 3.1.26 onward is not.

Remediation

Update to version 3.1.26, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber 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: FULL 3.1.26 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-12023https://www.wordfence.com/threat-intel/vulnerabilities/id/86e990ae-6bfe-4f2b-8c37-b0675430a638https://nvd.nist.gov/vuln/detail/CVE-2024-12023

Related records

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