dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-47225

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in KaizenCoders Short URL shorten-url allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Short URL: from n/a through <= 1.6.8.

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

The KaizenCoders Short URL plugin for WordPress (versions <= 1.6.8) contains a missing authorization vulnerability allowing exploitation of incorrectly configured access control security levels. This IDOR/broken access control flaw permits users with lower privileges to perform actions or access data that should be restricted to higher-privilege users, likely through missing capability checks on certain AJAX endpoints or admin functions.

MitigationUpgrade the Short URL plugin to version 1.6.9 or later which implements proper capability checks and authorization validation on all sensitive functions and endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 plugin installation
    Navigate to WordPress admin dashboard > Plugins and locate 'Short URL' by KaizenCoders, or check via WP-CLI: wp plugin list --name='short-url'
    Affected if The plugin is not installed or not present in the plugin list
  2. Identify installed version
    In Plugins list, check the version column next to Short URL plugin, or use WP-CLI: wp plugin get short-url --format=json
    Affected if Version is 1.6.8 or lower (any version up to and including 1.6.8)
  3. Verify plugin files exist
    Check plugin directory /wp-content/plugins/short-url/ exists and contains core files such as short-url.php, or run: ls -la /path/to/wp-content/plugins/short-url/
    Affected if Plugin files are present on the filesystem
  4. Test for missing capability checks
    Attempt to access plugin AJAX endpoints (typically /wp-admin/admin-ajax.php?action=kaizencoders_shorturl_*) using a low-privilege user account (subscriber or contributor role) without proper capability verification
    Affected if Lower-privilege users can execute admin-level functions or access sensitive plugin data without rejection

If the Short URL plugin version is 1.6.8 or lower and lower-privilege users can access admin functions, the environment is affected by this broken access control vulnerability.

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 the Short URL plugin to version 1.6.9 or later which implements proper capability checks and authorization validation on all sensitive functions and endpoints.

Have this fixed 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 help mitigating

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-2023-47225 — 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-2023-47225 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