CVE-2023-40678
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 · uneditedMissing Authorization vulnerability in Andrew Fiebert Simple URLs simple-urls allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Simple URLs: from n/a through <= 117.
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 confidenceThe Simple URLs WordPress plugin (versions <=117) by Andrew Fiebert contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthenticated or unauthorized users to access URL management functionality that should be restricted.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Simple URLs plugin is installedNavigate to WordPress admin > Plugins and confirm Simple URLs appears in the list of installed plugins, or inspect the directory /wp-content/plugins/simple-urls/ for the plugin filesAffected if The plugin is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin > Plugins, locate Simple URLs and view the version number displayed under the plugin name, or open the main plugin PHP file and check the 'Version' header commentAffected if The installed version is 117 or lower (any version up to and including 117)
-
Identify URL management endpointsInspect plugin PHP files in /wp-content/plugins/simple-urls/ for action handlers (typically add_action or wp_ajax_ hooks) that handle URL creation, editing, or deletion - look for functions processing form submissions without current_user_can() checksAffected if The plugin contains URL management functionality (add/edit/delete) that lacks capability verification (current_user_can checks) before processing requests
-
Test for unauthenticated access to URL actionsIf accessible, send a direct POST request to the plugin AJAX endpoints (typically /wp-admin/admin-ajax.php with action=simple_urls_*) without providing authentication credentials, or observe if the plugin accepts such requestsAffected if The plugin processes URL management requests from unauthenticated or unauthorized users without validating user capabilities
A WordPress installation is affected if the Simple URLs plugin version is 117 or lower and the plugin handles URL management without verifying that the requesting user has appropriate WordPress capabilities.
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 Simple URLs plugin to a version beyond 117 which contains proper authorization checks, or implement role-based access control and capability checks on all sensitive plugin endpoints.
- 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-40678 — 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-40678 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