dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-31640

HIGH · 8.5 CVSS v3.1 Published 2025-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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 LambertGroup Magic Responsive Slider and Carousel WordPress magic-carousel allows SQL Injection.This issue affects Magic Responsive Slider and Carousel WordPress: from n/a through < 1.6.

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 the Magic Responsive Slider and Carousel WordPress plugin allows attackers to inject malicious SQL commands via unsanitized input parameters. The vulnerability affects all versions before 1.6 and could enable unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate the Magic Responsive Slider and Carousel plugin to version 1.6 or later. If update is not possible immediately, disable the plugin and review database logs for signs of exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 files
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'magic-responsive-slider' or 'magic-responsive-slider-and-carousel'
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed version
    Open the main plugin PHP file (usually named similar to magic-responsive-slider.php) and look for the 'Version' header in the plugin comment block, or check the plugin's readme.txt file
    Affected if The version listed is below 1.6 (e.g., 1.5, 1.4, 1.0)
  3. Confirm the plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and verify whether Magic Responsive Slider and Carousel is activated
    Affected if The plugin shows as 'Active' status
  4. Check for suspicious database queries in logs
    Review WordPress debug logs (wp-content/debug.log if logging is enabled) or server access/error logs for unusual SQL syntax or patterns like UNION SELECT, OR 1=1, or DROP TABLE appearing in URL parameters
    Affected if Log entries show SQL injection payloads in requests to the plugin's endpoints

The environment is affected if the Magic Responsive Slider and Carousel plugin is installed, active, and running a version lower than 1.6, with SQL injection payloads potentially present in server or database logs indicating exploitation attempts.

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 Magic Responsive Slider and Carousel plugin to version 1.6 or later. If update is not possible immediately, disable the plugin and review database logs for signs of exploitation.

Recommended fix Moderate confidence

version 1.6

  1. Backup your WordPress site before making any changes
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate 'Magic Responsive Slider and Carousel' by LambertGroup
  5. Click 'Update now' if an update is available, or manually upload version 1.6
  6. After updating, verify the plugin is active and functioning correctly
  7. Test carousel and slider functionality to ensure the plugin works as expected

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-31640 — 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-31640 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