dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-13673

HIGH · 7.5 CVSS v3.1 Published 2026-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to SQL Injection via the 'coupon_code' parameter in all versions up to, and including, 3.9.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. NOTE: This vulnerability was partially mitigated in versions 3.9.4 and 3.9.6.

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 is vulnerable to SQL injection via the 'coupon_code' parameter in versions up to 3.9.6. The vulnerability results from insufficient escaping of user input combined with lack of prepared statements in the SQL query, allowing unauthenticated attackers to inject arbitrary SQL commands and exfiltrate sensitive database information.

MitigationUpdate to the latest version of Tutor LMS beyond 3.9.6 where the SQL injection vulnerability is fully patched, ensuring the coupon_code parameter is properly sanitized and SQL queries use prepared statements.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Tutor LMS plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Tutor LMS' (or 'TutorLMS'). Note the version number displayed. Alternatively, check the plugin's main PHP file header for the 'Version' tag, typically in tutor.php or class-tutor.php within the plugin directory.
    Affected if The installed version is 3.9.6 or lower.
  2. Confirm the coupon functionality is exposed
    Identify if the site uses Tutor LMS coupon features. Check wp_options for 'tutor_coupon' related settings, or look for frontend pages containing 'coupon' or 'discount' forms. The vulnerable endpoint typically handles coupon_code validation during checkout or enrollment.
    Affected if Coupons are enabled and the coupon_code parameter is processed via the Tutor LMS checkout or enrollment flow.
  3. Identify the vulnerable code path
    Locate the file handling the coupon_code parameter. In affected versions, this is typically in tutor/templates/enroll-button.php or tutor/includes/ajax.php around the 'apply_coupon' or 'verify_coupon' action. Search the plugin source for 'coupon_code' being used directly in SQL queries without prepare() or esc_sql().
    Affected if The coupon_code parameter is passed directly into an SQL query without prepared statements or proper escaping.
  4. Test for SQL injection vulnerability
    If you have access to the site, observe the HTTP request when applying a coupon. The parameter 'coupon_code' is sent via POST or GET to an AJAX handler. Attempt a benign injection test (e.g., ' OR '1'='1) in a staging environment and monitor for SQL errors or unexpected behavior in the response.
    Affected if The application returns SQL syntax errors or behaves differently based on injected SQL characters in the coupon_code parameter.

You are affected if Tutor LMS version 3.9.6 or lower is installed AND the coupon feature is active, allowing the coupon_code parameter to reach an unprepared SQL query.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Tutor LMS beyond 3.9.6 where the SQL injection vulnerability is fully patched, ensuring the coupon_code parameter is properly sanitized and SQL queries use prepared statements.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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