dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-12023

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FULL – Cliente WordPress plugin (versions 3.1.5-3.1.25) contains a SQL injection vulnerability in the 'formId' parameter. The plugin fails to properly escape user-supplied input and does not use prepared statements, allowing authenticated attackers with Subscriber-level access to inject malicious SQL queries. Exploitation requires the PRO version along with Elementor Pro and Elementor CRM to be active.

MitigationUpdate the plugin to a version beyond 3.1.25 when available. Until then, consider disabling the PRO version and related Elementor integrations if possible, or implement web application firewall rules to mitigate SQL injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if FULL - Cliente plugin is installed
    Navigate to WordPress admin > Plugins and look for 'FULL - Cliente' or run: wp plugin list --name='full-cliente'
    Affected if Plugin is not installed means not affected
  2. Check installed plugin version
    In WordPress admin > Plugins > FULL - Cliente, view the version number. Compare against affected range: 3.1.5 through 3.1.25
    Affected if Version falls between 3.1.5 and 3.1.25 inclusive indicates potentially affected
  3. Verify if PRO version is active
    Check plugin settings or status page for FULL - Cliente PRO activation status, or inspect plugin files for PRO-specific modules
    Affected if PRO version is active and running required for exploit to work
  4. Confirm Elementor Pro is installed and active
    Go to WordPress admin > Plugins and verify Elementor Pro is installed and activated
    Affected if Elementor Pro must be active alongside the plugin for vulnerability to be exploitable
  5. Confirm Elementor CRM is installed and active
    Check WordPress plugins list for Elementor CRM integration, or verify CRM module is enabled within FULL - Cliente settings
    Affected if Elementor CRM must be active for the vulnerability to be exploitable

Environment is affected only if FULL - Cliente plugin version is 3.1.5-3.1.25 AND the PRO version is active AND both Elementor Pro and Elementor CRM are enabled simultaneously.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 3.1.25 when available. Until then, consider disabling the PRO version and related Elementor integrations if possible, or implement web application firewall rules to mitigate SQL injection attempts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12023 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data