CVE-2025-6064
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 · uneditedThe WP URL Shortener plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation on the 'url_shortener_settings' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe WP URL Shortener plugin for WordPress lacks proper nonce validation on its settings page (url_shortener_settings), allowing unauthenticated attackers to forge administrative requests. This CSRF flaw enables attackers to modify plugin settings and inject malicious scripts by tricking administrators into clicking crafted links.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm WP URL Shortener plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-url-shortener', 'url-shortener', or similar. Alternatively, log into WordPress admin and navigate to Plugins to see if WP URL Shortener appears in the list.Affected if The plugin is not listed in the installed plugins.
-
Identify the installed plugin versionIf the plugin is installed, open its main PHP file (often named url-shortener.php, wp-url-shortener.php, or similar in the plugin folder) and look for the version comment in the file header. Alternatively, check the plugin's readme.txt file for the Version field.Affected if The version found is earlier than 1.3, or the version cannot be determined.
-
Locate the settings page handlerIn the plugin files, search for the string 'url_shortener_settings' to find the settings page callback function. This is typically in the main plugin file or a separate admin class file.Affected if The settings page handler exists and processes save requests.
-
Verify nonce validation is missingExamine the settings save function identified in the previous step. Look for wp_nonce_field, wp_verify_nonce, or check_admin_referer calls. Determine if a valid nonce is required before processing settings changes.Affected if The settings save function does not verify a nonce token before processing administrative changes, allowing forged requests.
A user is affected if the WP URL Shortener plugin is installed with a version earlier than 1.3 and the plugin's settings page lacks proper nonce validation, enabling CSRF attacks on administrators.
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 dataUpdate the plugin to version 1.3 or later once available. In the meantime, advise administrators to avoid clicking untrusted links and manually audit plugin settings for any unauthorized changes.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6064 — 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-2025-6064 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