dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32204

HIGH · 7.6 CVSS v3.1 Published 2025-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in rocketelements Split Test For Elementor split-test-for-elementor allows SQL Injection.This issue affects Split Test For Elementor: from n/a through <= 1.8.3.

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

SQL Injection vulnerability in rocketelements Split Test For Elementor plugin allows attackers to inject malicious SQL commands via unsanitized input in the split-test-for-elementor functionality, potentially enabling data exfiltration or database manipulation.

MitigationUpgrade to a patched version of the plugin that implements proper input sanitization and uses prepared statements for all database queries. If no patched version exists, disable the plugin until a fix is available.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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. Locate the plugin and identify its version
    In WordPress admin, go to Plugins > Installed Plugins > find 'Split Test For Elementor' (may appear as 'Split Test For Elementor' or 'rocketelements Split Test For Elementor'). Note the version number displayed under the plugin name. Alternatively, check the plugin main file (wp-content/plugins/split-test-for-elementor/split-test-for-elementor.php) for the 'Version' header in the plugin comment block.
    Affected if The installed version is older than the version that includes proper input sanitization and prepared statements.
  2. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that 'Split Test For Elementor' shows as 'Active' under its status.
    Affected if The plugin is active, making the vulnerable code reachable via web requests.
  3. Identify the vulnerable endpoint
    Examine the plugin PHP files (typically in wp-content/plugins/split-test-for-elementor/) for functions handling the 'split-test-for-elementor' AJAX actions or front-end submissions. Look for direct SQL queries using $wpdb->prepare or similar without proper sanitization of user-supplied parameters.
    Affected if The plugin contains unsanitized SQL queries in files that handle split-test functionality.
  4. Check for suspicious database activity
    Review WordPress debug logs (wp-content/debug.log if logging is enabled) or database query logs for unusual or malformed SQL queries originating from the plugin. Also check the wp_options table or any custom tables created by the plugin for unexpected entries.
    Affected if Database contains suspicious queries or data consistent with SQL injection attempts.
  5. Inspect web server access logs
    Review Apache/Nginx access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests to the plugin endpoint containing SQL metacharacters (', ", UNION, SELECT, --, etc.) in parameters related to split-test functionality.
    Affected if Access logs show requests with SQL injection patterns targeting the plugin.

A user is affected if the Split Test For Elementor plugin is installed, active, and running a version that lacks proper input sanitization and prepared statements in its SQL queries.

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

Upgrade to a patched version of the plugin that implements proper input sanitization and uses prepared statements for all database queries. If no patched version exists, disable the plugin until a fix is available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32204 — 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-2025-32204 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