dbcve.org
ShoplentorWordPress extension · Hasthemes

CVE-2025-11823

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-25
Fix available
A fix is available. Upgrade to 3.2.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 – WooCommerce Builder for Elementor & Gutenberg +21 Modules – All in One Solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'button_exist_text' parameter in the 'wishsuite_button' shortcode in all versions up to, and including, 3.2.4 due to insufficient input sanitization and output escaping. 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 (ShopLentor) plugin for WordPress contains a stored XSS vulnerability in the 'wishsuite_button' shortcode's 'button_exist_text' parameter. Due to insufficient input sanitization and output escaping, authenticated users with Contributor-level permissions can inject arbitrary JavaScript that executes when other users access affected pages.

MitigationUpdate the ShopLentor plugin to version 3.2.5 or later. Until patched, avoid using the 'wishsuite_button' shortcode or manually review pages using this shortcode for malicious content.

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
ShoplentorWordPress extension
Affected:< 3.2.5

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
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 checks

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

  1. Verify ShopLentor plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'ShopLentor' or 'Hasthemes Shoplentor' in the installed plugins list. Note the displayed version number.
    Affected if The plugin appears in the installed plugins list with a version number below 3.2.5
  2. Confirm the installed version number
    In the Plugins list, check the version column for ShopLentor. Compare this version against the affected range (< 3.2.5).
    Affected if The installed version is any version lower than 3.2.5 (e.g., 3.2.4, 3.2.0, 2.x, etc.)
  3. Check for use of the wishsuite_button shortcode
    In WordPress Admin, go to Pages and Posts. Search for content containing the text '[wishsuite_button' to identify pages or posts using this shortcode.
    Affected if Any page or post contains the [wishsuite_button shortcode and the plugin version is below 3.2.5
  4. Inspect shortcode content for suspicious attributes
    Edit pages or posts using the wishsuite_button shortcode. Review the shortcode parameters, particularly any 'button_exist_text' attribute, for unexpected characters like <script>, javascript:, or HTML tags.
    Affected if The button_exist_text parameter contains unsanitized or encoded content that could execute as JavaScript when the page is viewed

You are affected if the ShopLentor plugin version is below 3.2.5 AND any pages or posts use the wishsuite_button shortcode with untrusted content in the button_exist_text parameter.

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
Upgrade available Upgrade to 3.2.5 or later
Fixed in 3.2.5
Interim mitigation

Update the ShopLentor plugin to version 3.2.5 or later. Until patched, avoid using the 'wishsuite_button' shortcode or manually review pages using this shortcode for malicious content.

Recommended fix High confidence

3.2.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the ShopLentor plugin in the list
  4. If an update is available, click 'Update Now' to update to version 3.2.5
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload version 3.2.5 of the ShopLentor plugin
  6. Verify the plugin version is 3.2.5 after updating

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

Fix this in Shoplentor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11823 — 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-2025-11823 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