CVE-2023-23896 is a medium severity missing authorization flaw (CVSS 5.4) in the URL Shortener by MyThemeShop WordPress plugin, affecting every version through 1.0.17. Patchstack lists no official patch, so check the plugin page for a newer release and consider replacing it. Check every site you run, because plugin copies on forgotten staging sites are easy to miss.
What's affected
- URL Shortener by MyThemeShop plugin, all versions up to and including 1.0.17, per the record and the Patchstack listing.
- Fixed version: Patchstack lists no official patch at the time we read it, so check the plugin page for a newer release.
- Severity: CVSS 3.1 score 5.4 Medium, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L.
The Patchstack page title says version 1.0.16 while the page body and the record say 1.0.17. We treat every version through 1.0.17 as affected.
How to check if you're exposed
If you manage the site with WP-CLI, list the plugin and its version:
wp plugin list --fields=name,version,status | grep -i mts-url-shortener
The plugin directory slug is mts-url-shortener. Without WP-CLI, open Plugins, Installed Plugins in the WordPress admin and read the version under the URL Shortener by MyThemeShop entry. Check every site you run, including staging copies and sites that sit behind a hosting dashboard you rarely open. Multisite networks should also check each subsite, because a plugin can be active on one and absent on another.
What to do now
- Find every WordPress site that has URL Shortener by MyThemeShop installed, including staging copies, and read the version.
- Look for a newer release on the plugin page. If none exists, deactivate the plugin or replace it with a maintained alternative.
- If the plugin has no maintainer, plan its replacement.
- If you cannot update right away, deactivate the plugin until you can.
- Review web server logs for unexpected requests to the plugin around the time you learned of the issue.
Why it matters
The weakness is missing authorization (CWE-862 (Missing Authorization)). Broken access control means a function runs without checking that the caller is allowed to use it. WordPress plugins register many actions that requests can reach, so each one needs an explicit capability check. When the check is missing, the plugin trusts the request, whatever role the requester holds.
The record shows low privileges are required and low integrity and availability impact. Because no official patch was listed when we read the Patchstack page, the safe options are to remove the plugin, replace it with a maintained alternative, or confirm that a newer release now exists. An unpatched plugin tends to stay unpatched. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.
Web application firewalls and managed WordPress hosts sometimes block known plugin attacks, but a rule is not a fix. Use any such protection as a bridge while you update, not a reason to postpone the update.
Quick check
What if there is no patch?
Deactivate and delete the plugin, then use a maintained alternative for short links, or move the function to a service outside WordPress.
Why do the sources show two version numbers?
The record says through 1.0.17, while the Patchstack page title says 1.0.16 and its details say 1.0.17. Treat 1.0.17 and earlier as affected.
Sources
Last reviewed: 19 October 2026.