Short UrlWordPress extension · Kaizencoders
CVE-2023-45058
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in KaizenCoders Short URL plugin <= 1.6.8 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the KaizenCoders Short URL WordPress plugin affecting versions up to and including 1.6.8. The plugin fails to properly validate anti-CSRF tokens on state-changing operations, allowing attackers to trick authenticated administrators into unknowingly performing unintended actions such as modifying short URLs or plugin settings.
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
<= 1.6.8CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the KaizenCoders Short URL plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'KaizenCoders Short Url' or check the main plugin file (usually short-url.php) in wp-content/plugins/ for the 'Version' header in the plugin commentsAffected if The displayed version is 1.6.8 or lower
-
Compare your installed version to the affected rangeReview the version number found in the previous step against the affected range: versions 1.6.8 and belowAffected if Your installed version is 1.6.8 or any lower number (e.g., 1.6.7, 1.6.0, 1.5.2)
-
Identify state-changing operations in the pluginExamine plugin PHP files for form submissions and action hooks that modify data (e.g., create_shorturl, save_settings, delete_url, update_url functions)Affected if The plugin contains forms or action handlers that perform database writes or settings changes without visible nonce field presence
-
Check for proper nonce validation in the plugin codeSearch plugin PHP files for 'wp_verify_nonce' or 'check_admin_referer' calls within the identified state-changing functionsAffected if State-changing functions lack nonce verification calls, or nonce checks are missing entirely
You are affected if the installed KaizenCoders Short Url plugin version is 1.6.8 or lower and state-changing operations lack proper anti-CSRF token validation.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to the latest version of the KaizenCoders Short URL plugin. Additionally, ensure proper nonce verification is implemented on all form submissions and action hooks, and consider adding Origin/Referer header validation as a defense-in-depth measure.
Fix this in Short Url
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-45058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45058 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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