dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49327

HIGH · 7.6 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Ruben Garcia ShortLinks Pro shortlinkspro allows SQL Injection.This issue affects ShortLinks Pro: from n/a through <= 1.0.7.

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 the ShortLinks Pro WordPress plugin allows remote attackers to inject malicious SQL commands through unsanitized user input in affected endpoints.

MitigationUpgrade to a patched version of ShortLinks Pro; if no patch is available, audit and refactor all database query code to use parameterized queries or prepared statements with proper input sanitization.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm ShortLinks Pro plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and locate ShortLinks Pro. Note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/shortlinks-pro/shortlinks-pro.php for the Version: X.X.X field.
    Affected if The plugin is installed and active.
  2. Determine the exact installed version
    Read the Version field from the plugin's main PHP file header or from the WordPress plugins page. Document this version number for comparison.
    Affected if The installed version cannot be determined or is unknown.
  3. Compare version against affected range
    Obtain the specific vulnerable version range from the official WordPress security advisory or vendor disclosure for CVE-2025-49327. Compare your installed version number against this range.
    Affected if Your installed version falls within the vulnerable version range.
  4. Identify affected plugin endpoints
    Review the plugin directory (wp-content/plugins/shortlinks-pro/) for PHP files handling user input. Look for files containing $_GET, $_POST, or $_REQUEST parameters passed to database queries without prepare() or esc_sql() functions.
    Affected if The plugin contains endpoints that process user input through unsanitized SQL queries.
  5. Inspect database query code
    Examine the plugin's PHP files for direct SQL queries using $wpdb->query(), $wpdb->get_results(), or similar without $wpdb->prepare(). Search for user-supplied parameters ($_GET, $_POST, $_REQUEST) used directly in query strings.
    Affected if User input from $_GET, $_POST, or $_REQUEST is concatenated directly into SQL queries without sanitization or prepared statements.
  6. Check for web access logs of suspicious activity
    Review web server access logs (Apache/nginx) for requests to ShortLinks Pro plugin endpoints containing SQL injection payloads (single quotes, UNION SELECT, OR 1=1, etc.) in URL parameters.
    Affected if Suspicious SQL injection patterns are found in logs targeting the plugin.

You are affected if ShortLinks Pro is installed with a version within the vulnerable range AND the plugin processes user input through unsanitized database queries in accessible endpoints.

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

Upgrade to a patched version of ShortLinks Pro; if no patch is available, audit and refactor all database query code to use parameterized queries or prepared statements with proper input sanitization.

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