dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4059

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The ShopLentor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the woolentor_quickview_button shortcode's button_text attribute in all versions up to, and including, 3.3.5. This is due to insufficient input sanitization and missing output escaping on user-supplied shortcode attributes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The ShopLentor WordPress plugin up to version 3.3.5 contains a stored XSS vulnerability in the woolentor_quickview_button shortcode. The button_text attribute lacks proper input sanitization and output escaping, allowing authenticated contributors+ to inject malicious JavaScript that executes when users view pages containing the shortcode.

MitigationUpgrade to version 3.3.6 or later. Until patched, restrict contributor-level access and audit existing pages for injected shortcodes.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ShopLentor plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for ShopLentor (or WooLentor) in the list
    Affected if ShopLentor plugin is present in the plugins list
  2. Identify installed ShopLentor version
    In Plugins list, click the plugin name to view version details, or check the plugin header in /wp-content/plugins/woolentor-addons/ directory
    Affected if Installed version is 3.3.5 or lower (any version up to 3.3.5 is vulnerable)
  3. Search for woolentor_quickview_button shortcode usage
    Search WordPress posts/pages content for the shortcode [woolentor_quickview_button] using WP admin search or database query: SELECT * FROM wp_posts WHERE post_content LIKE '%woolentor_quickview_button%'
    Affected if The shortcode is present in any published content
  4. Inspect button_text attribute values
    Examine the shortcode usage in page content: look for button_text="..." and check if the value contains unescaped HTML or JavaScript (quotes, script tags, event handlers)
    Affected if button_text attribute contains raw user-controlled text with special characters like < > " or javascript:
  5. Check for contributor-level user accounts
    In WordPress admin, go to Users and review roles; contributors have limited editing access but can create shortcodes
    Affected if Any user with contributor role or higher (excluding admin) exists on the site who could have injected the malicious shortcode

User is affected if ShopLentor version is 3.3.5 or below AND the woolentor_quickview_button shortcode with a potentially malicious button_text attribute exists in any published content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 3.3.6 or later. Until patched, restrict contributor-level access and audit existing pages for injected shortcodes.

Recommended fix Moderate confidence

ShopLentor version higher than 3.3.5

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find ShopLentor (formerly WooLentor) plugin
  4. Click 'Update now' if an update is available, or download the latest version from wordpress.org
  5. Verify the update to a version higher than 3.3.5 was applied successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4059 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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