Simple UrlsWordPress extension · Getlasso
CVE-2023-40667
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Lasso Simple URLs plugin <= 117 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 confidenceAn unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the Lasso Simple URLs WordPress plugin affecting versions 117 and below. The vulnerability allows attackers to inject malicious scripts through reflected parameters, which are executed in the victim's browser when they interact with a crafted link.
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
Simple UrlsWordPress extension
<= 117CVSS 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.
-
Identify if Lasso Simple URLs plugin is installedAccess your WordPress site via FTP or file manager and check the wp-content/plugins/ directory for a folder named 'simple-urls', 'lasso', or 'getlasso-simple-urls'. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to look for 'Simple URLs' or 'Lasso Simple URLs'.Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugin list.
-
Determine the installed plugin versionIf the plugin is installed, open the main plugin PHP file (typically simple-urls.php or lasso-simple-urls.php) in the plugin folder and locate the 'Version' field in the plugin header comment at the top of the file.Affected if The version number displayed is 117 or lower (for example: 117, 116, 115, 100, etc.).
-
Verify if the plugin is activeLog into WordPress admin and check the Plugins page, or query the WordPress database table wp_options for the option_name 'active_plugins' to see if the plugin is enabled.Affected if The plugin version is 117 or below AND the plugin is currently activated on the site.
-
Review web server access logs for exploitation indicatorsSearch your web server access logs (Apache, Nginx, or your hosting provider's log viewer) for GET or POST requests to your WordPress site that contain suspicious script tags or javascript: URLs in query parameters, particularly targeting URLs with 'simple-urls', 'redirect', or similar parameter names.Affected if Log entries show requests with reflected XSS payloads (such as <script> tags, javascript:, or event handlers like onerror/onload) in URL parameters.
You are affected if the Lasso Simple URLs plugin is installed, active, and the version is 117 or below; if exploitation is suspected, check server logs for malicious parameter injection attempts.
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 Lasso Simple URLs plugin to the latest version if a patch is available; otherwise, disable the plugin until a fix can be applied. Additionally, implement output encoding and input validation as a defense-in-depth measure.
Fix this in Simple Urls
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40667 — 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-40667 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