dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-2011

HIGH · 7.5 CVSS v3.1 Published 2025-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Slider & Popup Builder by Depicter plugin for WordPress is vulnerable to generic SQL Injection via the ‘s' parameter in all versions up to, and including, 3.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Depicter WordPress plugin versions up to 3.6.1 contain an unauthenticated SQL injection vulnerability via the 's' parameter. The plugin fails to properly escape user input and does not use prepared statements, allowing attackers to inject arbitrary SQL queries and extract sensitive database information.

MitigationUpdate the Depicter plugin to version 3.6.2 or later immediately. If immediate updating is not feasible, disable the plugin or deploy a WAF rule to block malicious 's' parameter requests.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the Depicter plugin and identify its version
    Access your WordPress admin panel and navigate to Plugins > Installed Plugins, locate Depicter, and note the version number displayed. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/depicter/) for the version header comment.
    Affected if The installed version is 3.6.1 or lower.
  2. Confirm the plugin is active
    In the WordPress plugins admin page, verify that Depicter shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is currently active and the version is 3.6.1 or lower.
  3. Determine if the search functionality is publicly accessible
    Attempt to access a page on your site that uses Depicter and append ?s=test to the URL (for example, yoursite.com/?s=test). This tests whether the 's' parameter is processed by the plugin without authentication.
    Affected if The site processes the 's' parameter and returns results without requiring login.
  4. Inspect HTTP responses for SQL error indicators
    Send a crafted request with a SQL injection payload in the 's' parameter (such as ?s=test' OR 1=1--) and observe whether the response contains SQL error messages, unusual database errors, or unexpected query results.
    Affected if The application returns SQL syntax errors or behaves unexpectedly when special characters are passed to the 's' parameter, indicating lack of proper input sanitization.

Your environment is affected if the Depicter plugin is active, installed at version 3.6.1 or lower, and the 's' parameter is processed without authentication.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Depicter plugin to version 3.6.2 or later immediately. If immediate updating is not feasible, disable the plugin or deploy a WAF rule to block malicious 's' parameter requests.

Recommended fix Moderate confidence

Version higher than 3.6.1 (check WordPress plugin repository for latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'Slider & Popup Builder by Depicter' plugin
  4. Check if the current version is 3.6.1 or below
  5. If vulnerable, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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