dbcve.org
ShoplentorWordPress extension · Hasthemes

CVE-2024-9538

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 2.9.9 or later.
See remediation →
71/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 Sensitive Information Exposure in all versions up to, and including, 2.9.8 via the 'render' function in includes/addons/wl_faq.php. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive private, pending, and draft Elementor template data.

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 has an IDOR/broken access control vulnerability in the wl_faq.php addon. The render function fails to properly authorize access to Elementor templates, allowing any authenticated user with Contributor-level permissions or higher to read private, pending, and draft templates that should be restricted to their authors or administrators.

MitigationUpdate ShopLentor to version 2.9.9 or later which contains proper authorization checks in the render function. If immediate update is not possible, disable the wl_faq addon until patched.

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:< 2.9.9

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 'Hasthemes ShopLentor' in the list. Note the installed version number displayed next to the plugin name.
    Affected if The plugin is installed and the version shown is below 2.9.9 (e.g., 2.9.8, 2.9.7, etc.)
  2. Verify wl_faq addon is active
    Navigate to ShopLentor settings in the WordPress admin (usually under WP Admin > ShopLentor or Plugins > ShopLentor). Look for the wl_faq addon module and check if it is enabled/active.
    Affected if The wl_faq addon is enabled in the ShopLento plugin settings
  3. Check for user role configuration
    In WordPress admin, go to Users > Users and review the roles assigned. Specifically check if there are users with Contributor-level permissions or higher who should not have access to private/draft Elementor templates.
    Affected if User accounts with Contributor, Author, or Editor roles exist in the system who should not have access to all template types
  4. Test template access via render function
    Using a low-privileged test account (Contributor level), attempt to access Elementor templates that are set to Private, Pending, or Draft status via the wl_faq render functionality. This may require inspecting network requests or direct URL access to template rendering endpoints.
    Affected if A Contributor-level user can view private, pending, or draft Elementor templates that they did not create

You are affected if ShopLentor version is below 2.9.9 AND the wl_faq addon is enabled AND lower-privileged users can access restricted Elementor templates through the render function.

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 2.9.9 or later
Fixed in 2.9.9
Interim mitigation

Update ShopLentor to version 2.9.9 or later which contains proper authorization checks in the render function. If immediate update is not possible, disable the wl_faq addon until patched.

Recommended fix High confidence

2.9.9

  1. Backup your WordPress site before making any changes
  2. Update the ShopLentor plugin to version 2.9.9 or higher
  3. Verify the update was successfully applied by checking the plugin version in WordPress admin

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

Fix this in Shoplentor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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