dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22655

CRITICAL · 9.3 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Caio Web Dev CWD – Stealth Links cwd-stealth-links allows SQL Injection.This issue affects CWD – Stealth Links: from n/a through <= 1.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 · moderate confidence

SQL Injection vulnerability in Caio Web Dev's CWD – Stealth Links WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user inputs in the plugin's database queries, potentially enabling unauthorized data extraction, modification, or complete database compromise.

MitigationReplace all dynamic SQL queries with parameterized queries (prepared statements) and implement proper input validation and sanitization for all user-supplied data before database interaction.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify if CWD - Stealth Links plugin is installed
    Access your WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'CWD - Stealth Links' or 'Stealth Links' by Caio Web Dev. Alternatively, check your wp-content/plugins directory for a folder named 'cwd-stealth-links' or similar.
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    In WordPress admin, click on the plugin name to view details and find the version number. Alternatively, open the main plugin file (usually stealth-links.php or cwd-stealth-links.php) and look for the 'Version' header in the plugin comments, or check the readme.txt file in the plugin folder.
    Affected if The installed version is unknown, unpatched, or falls within any vulnerable version range
  3. Check if plugin database tables exist
    Access your WordPress database via phpMyAdmin or command line and run: SHOW TABLES LIKE '%stealth%'; or SHOW TABLES LIKE 'wp_%stealth%'; This indicates the plugin has created database tables that process user input.
    Affected if Stealth Links-related database tables exist and the plugin is active
  4. Inspect plugin source code for unsanitized SQL queries
    Examine the main plugin PHP files (especially those handling form submissions, user inputs, or database operations) for direct use of $_GET, $_POST, or $_REQUEST in SQL queries without $wpdb->prepare(), esc_sql(), or similar sanitization functions.
    Affected if Dynamic SQL queries accept user input without parameterization or escaping
  5. Review WordPress and server logs for SQL injection attempts
    Check wp-content/debug.log (if debug logging is enabled), server error logs, and WordPress activity logs for suspicious SQL syntax in requests to pages using the Stealth Links functionality.
    Affected if Logs show SQL injection payloads or anomalous SQL errors originating from Stealth Links endpoints
  6. Check for unauthorized database access or data exfiltration
    Query your database for unexpected changes: SELECT * FROM wp_options WHERE option_name NOT LIKE '%stealth%'; Also check for new admin users or modified user capabilities: SELECT * FROM wp_users WHERE user_login NOT IN (known_admin_accounts);
    Affected if Unusual database entries, unknown admin accounts, or modified plugin data are found

You are affected if the CWD - Stealth Links plugin is installed and its SQL queries process user input without proper sanitization or parameterized 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

Replace all dynamic SQL queries with parameterized queries (prepared statements) and implement proper input validation and sanitization for all user-supplied data before database interaction.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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