dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10738

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-13
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
The URL Shortener Plugin For WordPress plugin for WordPress is vulnerable to SQL Injection via the ‘analytic_id’ parameter in all versions up to, and including, 3.0.7 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 URL Shortener Plugin For WordPress is vulnerable to SQL Injection via the unauthenticated 'analytic_id' parameter in versions up to 3.0.7. The plugin fails to properly escape user input and does not use prepared statements when constructing SQL queries, allowing attackers to inject arbitrary SQL code and potentially extract sensitive database information.

MitigationUpdate the URL Shortener Plugin for WordPress to version 3.0.8 or later which contains the fix. If immediate updating is not possible, consider disabling the plugin until a patched version is available.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm URL Shortener plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'url-shortener' or similar, or query the wp_options table for 'active_plugins' to see if the plugin is enabled
    Affected if The plugin folder exists in plugins directory or the plugin is listed in active site-wide or network-active plugins
  2. Identify the installed plugin version
    Read the plugin header from the main PHP file (e.g., url-shortener.php) to find the 'Version:' tag, or query the wp_options table for option_name='active_plugins' and examine plugin file headers
    Affected if The version number found is 3.0.7 or lower (any version up to and including 3.0.7)
  3. Determine if the analytics tracking feature is accessible
    Probe the endpoint that processes the 'analytic_id' parameter - this is typically exposed via a shortcode callback, AJAX action, or frontend URL that accepts this parameter for tracking link clicks
    Affected if The plugin exposes any public-facing functionality that accepts and processes an 'analytic_id' parameter without authentication
  4. Check for signs of SQL injection exploitation
    Review WordPress debug logs (wp-content/debug.log if enabled), server access logs, and the wp_options table for any unusual or malformed SQL syntax entries, or check for unexpected new user accounts or modified content
    Affected if SQL error messages, suspicious database queries in logs, or unauthorized database changes are observed that correlate with the analytic_id parameter

You are affected if the URL Shortener plugin is installed with version 3.0.7 or lower AND the analytics feature that uses the analytic_id parameter is publicly accessible.

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 URL Shortener Plugin for WordPress to version 3.0.8 or later which contains the fix. If immediate updating is not possible, consider disabling the plugin until a patched version is available.

Recommended fix Moderate confidence

Latest version after 3.0.7 (check wordpress.org for current release)

  1. Update the URL Shortener Plugin For WordPress to the latest available version from the WordPress plugin repository

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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