Simple UrlsWordPress extension · Getlasso
CVE-2023-40674
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Lasso Simple URLs – Link Cloaking, Product Displays, and Affiliate Link Management allows Stored XSS.This issue affects Simple URLs – Link Cloaking, Product Displays, and Affiliate Link Management: from n/a through 118.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the Lasso Simple URLs WordPress plugin (versions up to 118). The vulnerability allows authenticated attackers with low privileges to inject malicious JavaScript code through plugin input fields, which is then stored in the database and executed when other users view affected pages.
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
<= 118CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Lasso Simple URLs plugin is installedNavigate to WordPress Admin > Plugins and look for 'Simple URLs' or 'Getlasso Simple URLs' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn WordPress Admin > Plugins, find Simple URLs and note the version number displayed below the plugin nameAffected if The version is 118 or lower (e.g., 118, 117, 116, etc.)
-
Verify the plugin is activeIn WordPress Admin > Plugins, confirm the Simple URLs plugin shows as 'Active' rather than 'Inactive'Affected if The plugin is currently active
-
Check if low-privilege users can access Simple URLs functionalityLog in as a user with Subscriber or Contributor role and attempt to access the Simple URLs admin menu (usually under Settings or a dedicated Simple URLs menu)Affected if Low-privilege users can access and submit data through the plugin's input forms
-
Inspect the database for suspicious stored contentQuery the WordPress database tables (likely wp_options or a custom simple_urls table) for any stored URLs or redirects containing script tags, javascript:, or unusual encodingAffected if The database contains entries with XSS payloads in URL fields
You are affected if the Simple URLs plugin is installed, active, running version 118 or lower, and low-privilege users can access its input functionality.
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 once available. Until then, limit administrative access to trusted users only and implement Content Security Policy headers to mitigate XSS execution.
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-40674 — 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-40674 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