CVE-2025-10740
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 URL Shortener Plugin For WordPress plugin for WordPress is vulnerable to unauthorized access to functionality provided by the API due to a missing capability check on the verifyRequest function in all versions up to, and including, 3.0.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify links.
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 URL Shortener Plugin For WordPress lacks a capability check on the verifyRequest function, allowing authenticated users with Subscriber-level access (the lowest privilege tier) to modify links they should not have access to. This is a broken access control vulnerability where the API endpoint does not verify the user's permissions before allowing link modification operations.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the URL Shortener Plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'URL Shortener Plugin' or 'URL Shortener' in the plugin list. Note the installed version displayed next to the plugin name.Affected if The plugin is installed and the version is lower than 3.0.8
-
Locate the verifyRequest function fileAccess the WordPress site files via FTP or file manager. Navigate to /wp-content/plugins/ and locate the URL Shortener plugin folder. Open the main plugin PHP file and search for the function named 'verifyRequest'.Affected if The verifyRequest function exists and lacks a capability check (look for 'current_user_can' or 'manage_options' or similar permission checks before link modification operations)
-
Check for Subscriber-level user accountsIn WordPress admin, go to Users > All Users. Review the list to identify any users with the 'Subscriber' role assigned.Affected if At least one user with Subscriber role exists and can access the WordPress login
-
Test API endpoint accessibilityIf you have access to the site's REST API or AJAX endpoints used by the plugin, examine the verifyRequest function to determine if it is hooked to an API route (such as /wp-json/ or admin-ajax.php) and whether it performs any permission verification before allowing link modifications.Affected if The verifyRequest function is exposed via an API endpoint without capability verification
You are affected if the URL Shortener Plugin version is below 3.0.8, the verifyRequest function lacks capability checks, and any Subscriber-level user account exists in the WordPress installation.
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 3.0.8 or later, which should include proper capability checks on the verifyRequest function. If no update is available, add a WordPress capability check (e.g., 'manage_options' or a custom capability) to verifyRequest before allowing link modifications.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10740 — 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-10740 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