dbcve.org
Tutor Lms Elementor AddonsWordPress extension · Themeum

CVE-2024-29913

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 2.1.4 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themeum Tutor LMS Elementor Addons allows Stored XSS.This issue affects Tutor LMS Elementor Addons: from n/a through 2.1.3.

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 confidence

A Stored Cross-Site Scripting (XSS) vulnerability exists in Themeum Tutor LMS Elementor Addons plugin versions up to 2.1.3. The plugin fails to properly sanitize user-supplied input during web page generation, allowing malicious JavaScript to be stored and executed when other users view affected pages. This occurs in the Elementor addon components where input data is rendered without adequate output encoding.

MitigationApply output encoding (esc_html, esc_attr, wp_kses) to all user-supplied data before rendering in the web page. Update to the latest patched version of Tutor LMS Elementor Addons when available. Consider implementing Content Security Policy headers as defense-in-depth.

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
Tutor Lms Elementor AddonsWordPress extension
Affected:< 2.1.4

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 if Themeum Tutor LMS Elementor Addons is installed
    Access your WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Tutor LMS Elementor Addons' or 'Themeum Tutor Lms Elementor Addons' in the list of active and inactive plugins.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the Plugins page, click on the plugin name to view details, or inspect the plugin header in the main plugin file (typically in wp-content/plugins/tutor-elementor-addons/ or similar naming) to find the Version field.
    Affected if The version number displayed is less than 2.1.4 (for example: 2.1.3, 2.1.2, 2.1.1, etc.)
  3. Confirm Elementor page builder is active
    Navigate to Plugins > Installed Plugins and verify that both the Tutor LMS Elementor Addons plugin and the Elementor website builder plugin are active.
    Affected if Elementor is active and being used with the Tutor LMS addon plugin
  4. Check for content created using Tutor LMS Elementor widgets
    Go to Pages or Posts in the WordPress admin, and review any pages edited with Elementor that include Tutor LMS course, lesson, or quiz widgets. Inspect the page content for any user-supplied fields that may have been saved.
    Affected if There are pages or course content created using Tutor LMS Elementor widgets that contain user-generated input
  5. Review stored content for potential XSS payloads
    Use the browser developer tools or a database query to examine saved course content, lesson descriptions, quiz questions, or any fields that accept user input in the Tutor LMS system. Look for script tags, javascript: URIs, or event handler attributes in the stored HTML.
    Affected if Stored content contains unsanitized HTML or script tags that would execute when viewed

Your environment is affected if the Tutor LMS Elementor Addons plugin version is below 2.1.4 and you are using Elementor to create or edit Tutor LMS course content with user-supplied input fields.

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.1.4 or later
Fixed in 2.1.4
Interim mitigation

Apply output encoding (esc_html, esc_attr, wp_kses) to all user-supplied data before rendering in the web page. Update to the latest patched version of Tutor LMS Elementor Addons when available. Consider implementing Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

2.1.4

  1. Back up your WordPress site before performing any updates
  2. Navigate to WordPress admin dashboard > Plugins
  3. Locate 'Tutor LMS Elementor Addons' in the installed plugins list
  4. Click 'Update now' or manually update to version 2.1.4
  5. Verify the plugin version shows 2.1.4 after updating
  6. Test that the Elementor addons functionality works correctly

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

Fix this in Tutor Lms Elementor Addons Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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