CVE-2025-10660
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 · uneditedThe WP Dashboard Chat plugin for WordPress is vulnerable to SQL Injection via the ‘id’ parameter in all versions up to, and including, 1.0.3 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 Contributor-level access and above, 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 · moderate confidenceThe WP Dashboard Chat WordPress plugin versions up to 1.0.3 contains a SQL Injection vulnerability in the 'id' parameter. Authenticated attackers with Contributor-level access or higher can exploit insufficient input sanitization and lack of prepared statements to inject malicious SQL queries and extract sensitive database information.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the WP Dashboard Chat pluginCheck your WordPress installation at wp-content/plugins/ for a folder named 'wp-dashboard-chat' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Dashboard Chat'.Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in your WordPress admin plugin list.
-
Identify the installed versionIn WordPress admin, click on the plugin name to view details and read the version number. Alternatively, open the main plugin PHP file (usually wp-dashboard-chat.php) and look for the 'Version' header in the plugin comment block.Affected if The version listed is 1.0.3 or any earlier version (the vulnerability affects versions up to 1.0.3).
-
Verify the plugin is activeIn WordPress admin under Plugins > Installed Plugins, confirm whether WP Dashboard Chat shows as 'Active' under the plugin status.Affected if The plugin is currently active - an inactive plugin would not be exploitable.
-
Confirm user role access existsNavigate to Users > All Users in WordPress admin and check if any accounts have the 'Contributor' role or higher (Author, Editor, Administrator).Affected if At least one user with Contributor-level access or higher exists on the site, as this role is required to exploit the SQL Injection in the 'id' parameter.
You are affected if the WP Dashboard Chat plugin is installed, active, and running version 1.0.3 or earlier, with at least one user holding Contributor-level access or higher.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest version if available; otherwise, implement proper prepared statements or parameterized queries for all database operations and add input validation for the 'id' parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10660 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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