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

CVE-2026-13443

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-01
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 7 weeks old

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 Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Lesson Attachment Title in all versions up to, and including, 3.9.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-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 Tutor LMS WordPress plugin fails to properly sanitize the Lesson Attachment Title field during input and escape it during output, creating a stored XSS vulnerability. Authenticated attackers with author-level or higher privileges can inject malicious JavaScript that executes in the browsers of users who access the affected lesson pages.

MitigationUpdate Tutor LMS to a version beyond 3.9.13 that addresses this vulnerability; alternatively, implement proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html/esc_attr) on the Lesson Attachment Title field.

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. Verify Tutor LMS plugin is installed
    In WordPress admin, go to Plugins > Instored Plugins and look for 'Tutor LMS' in the list. Alternatively, check the wp-content/plugins directory for a tutor-lms folder.
    Affected if The Tutor LMS plugin is not installed on the WordPress site.
  2. Identify installed Tutor LMS version
    In WordPress admin, go to Plugins > Installed Plugins > Tutor LMS and view the 'Version' field. Alternatively, check the version constant in tutor-lms/version.php or the plugin header in tutor-lms/main.php.
    Affected if The installed version is 3.9.13 or lower.
  3. Confirm Lesson Attachment feature is in use
    Navigate to WordPress admin > Tutor LMS > Lessons. Edit any lesson and locate the 'Attachments' section. Check if any attachments have a Title field populated.
    Affected if The Lesson Attachment Title field contains user-supplied content (the vulnerable input field exists).
  4. Inspect database for suspicious payloads in attachment titles
    Query the WordPress database: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%attachment%title%' (adjust prefix if wp_ is different). Look for script tags, javascript:, onerror, or other XSS patterns in meta_value.
    Affected if The database contains unsanitized JavaScript or HTML in attachment title meta values.
  5. Verify user privilege levels
    In WordPress admin > Users, review which users have Author, Editor, or Administrator roles. These roles can access the Lesson editor and attachment functionality.
    Affected if There are users with Author-level or higher access who could have injected malicious content.

A site is affected if Tutor LMS version 3.9.13 or lower is installed AND the Lesson Attachment feature has been used with user-supplied titles, potentially containing injected XSS payloads in the database.

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

Update Tutor LMS to a version beyond 3.9.13 that addresses this vulnerability; alternatively, implement proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html/esc_attr) on the Lesson Attachment Title field.

Recommended fix Moderate confidence

Upgrade to Tutor LMS version 3.9.14 or latest available release

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Tutor LMS plugin in the list
  4. 4. If the current version is 3.9.13 or earlier, click 'Update Now' to install the latest available version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository at wordpress.org/plugins/tutorlms/ and upload it manually
  6. 6. After updating, verify the version number reflects the new release
  7. 7. Test that the Lesson Attachment functionality works correctly and that the XSS payload no longer executes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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