dbcve.org
Short UrlWordPress extension · Kaizencoders

CVE-2022-46860

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 1.6.5 or later.
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 KaizenCoders Short URL allows SQL Injection.This issue affects Short URL: from n/a through 1.6.4.

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

SQL injection vulnerability in KaizenCoders Short URL plugin allows attackers to inject malicious SQL commands through unsanitized user input, potentially allowing unauthorized database access, data exfiltration, or data manipulation.

MitigationUpdate to the latest version of the Short URL plugin and implement parameterized queries/prepared statements for all database operations; conduct thorough input validation and sanitization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Short UrlWordPress extension
Affected:< 1.6.5

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. Identify if Kaizencoders Short Url plugin is installed
    Access your WordPress site's plugins directory or admin panel and look for the Short Url plugin by Kaizencoders in the installed plugins list
    Affected if The plugin appears in your plugins list
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Short Url, and note the version number displayed below the plugin name
    Affected if The version shown is lower than 1.6.5 (e.g., 1.6.4, 1.6.0, etc.)
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm the Short Url plugin shows as Active
    Affected if The plugin is enabled and running on the site
  4. Inspect database query code for unsanitized input
    If you have file access, examine the plugin's PHP files (typically in wp-content/plugins/short-url/) for database queries that use raw user input without prepare() statements or escaping functions
    Affected if Database queries accept direct user input without sanitization
  5. Check web server logs for suspicious SQL-like patterns
    Review access logs for the plugin's endpoints looking for SQL metacharacters (quotes, semicolons, UNION, SELECT, --) in query parameters
    Affected if Logs show SQL injection attempts or unusual SQL syntax in requests to short URL endpoints

Your environment is affected if the Kaizencoders Short Url plugin is installed, active, and running version 1.6.4 or lower.

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
Upgrade available Upgrade to 1.6.5 or later
Fixed in 1.6.5
Interim mitigation

Update to the latest version of the Short URL plugin and implement parameterized queries/prepared statements for all database operations; conduct thorough input validation and sanitization.

Recommended fix High confidence

Short URL version 1.6.5

  1. Back up your WordPress database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find the 'Short URL' plugin by KaizenCoders
  4. Click 'Update now' if an update is available, or manually download version 1.6.5 from the WordPress plugin repository and upload it
  5. After updating, verify the plugin is running version 1.6.5 in the plugins list
  6. Test that the short URL functionality works correctly after the update

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

Fix this in Short Url Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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