dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-60110

HIGH · 8.5 CVSS v3.1 Published 2025-09-26
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 AllInOne - Banner Rotator all-in-one-bannerRotator allows SQL Injection.This issue affects AllInOne - Banner Rotator: from n/a through <= 3.8.

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 · moderate confidence

SQL injection vulnerability in LambertGroup AllInOne - Banner Rotator plugin allows attackers to inject malicious SQL commands through unsanitized input, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements; implement proper input validation and output encoding on all user-supplied data before database operations.

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. Identify if LambertGroup Banner Rotator plugin is installed
    Check your web application for the presence of the AllInOne Banner Rotator plugin directory or files (commonly found in /wp-content/plugins/ or similar plugin directories). Look for files named 'banner-rotator', 'all-in-one-banner', or LambertGroup-related directories.
    Affected if The plugin directory or files exist in your web application's plugin folder.
  2. Determine the installed plugin version
    Locate the plugin's main PHP file or a readme/version file within the plugin directory. Open the main plugin file and search for a version constant, variable, or header comment that states the version number.
    Affected if The version found matches any version of the LambertGroup AllInOne Banner Rotator plugin (no specific safe version range is documented for this CVE).
  3. Inspect user input handling in plugin code
    Search the plugin source code for PHP files that handle user-supplied data (look for $_GET, $_POST, $_REQUEST, or $_COOKIE superglobals). Identify which parameters are used in database queries.
    Affected if User input parameters are directly concatenated into SQL queries without sanitization, parameterization, or use of prepared statements.
  4. Check database query implementation for SQL injection flaws
    Review all database query functions in the plugin (mysql_query, mysqli_query, $wpdb->prepare, $wpdb->query, PDO statements). Verify if user-controlled variables are embedded directly into SQL strings.
    Affected if SQL queries contain unsanitized user input, such as string concatenation or interpolation of $_POST/$_GET values directly into query text.
  5. Test for SQL injection entry points
    If authorized and in a non-production environment, identify form fields, URL parameters, or API endpoints provided by the plugin. Attempt to inject SQL meta-characters (e.g., single quote, UNION SELECT) into plugin-related parameters and observe database behavior or error responses.
    Affected if The application returns database errors, unexpected data, or exhibits behavior indicating SQL injection is possible through plugin parameters.

Your environment is affected if the LambertGroup AllInOne - Banner Rotator plugin is installed and its code contains SQL queries that incorporate unsanitized user input directly into database operations.

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

Replace dynamic SQL queries with parameterized queries or prepared statements; implement proper input validation and output encoding on all user-supplied data before database operations.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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