dbcve.org
Tin Canny Reporting For LearndashApplication · Uncannyowl

CVE-2020-9439

MEDIUM · 6.1 CVSS v3.1 Published 2020-12-23
Fix available
A fix is available. Upgrade to 3.4.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Multiple cross-site scripting (XSS) vulnerabilities in Uncanny Owl Tin Canny LearnDash Reporting before 3.4.4 allows authenticated remote attackers to inject arbitrary web script or HTML via the search_key GET Parameter in TinCan_Content_List_Table.php, message GET Parameter in licensing.php, tc_filter_group parameter in reporting-admin-menu.php, tc_filter_user parameter in reporting-admin-menu.php, tc_filter_course parameter in reporting-admin-menu.php, tc_filter_lesson parameter in reporting-admin-menu.php, tc_filter_module parameter in reporting-admin-menu.php, tc_filter_action parameter in reporting-admin-menu.php, tc_filter_data_range parameter in reporting-admin-menu.php, or tc_filter_data_range_last parameter in reporting-admin-menu.php.

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

Multiple cross-site scripting (XSS) vulnerabilities exist in Uncanny Owl Tin Canny LearnDash Reporting plugin versions before 3.4.4. Authenticated attackers can inject arbitrary web script or HTML via multiple GET parameters (search_key, message, tc_filter_group, tc_filter_user, tc_filter_course, tc_filter_lesson, tc_filter_module, tc_filter_action, tc_filter_data_range, tc_filter_data_range_last) across TinCan_Content_List_Table.php, licensing.php, and reporting-admin-menu.php files.

MitigationUpdate the Tin Canny LearnDash Reporting plugin to version 3.4.4 or later, which includes proper input sanitization for the affected GET parameters.

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
Tin Canny Reporting For LearndashApplication
Affected:< 3.4.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Instored Plugins. Locate 'Tin Canny Reporting for LearnDash' by Uncanny Owl and note the installed version number.
    Affected if The plugin is installed and the version displayed is lower than 3.4.4 (e.g., 3.4.3, 3.4.2, etc.)
  2. Confirm affected PHP files exist
    Access the WordPress site via file manager or FTP. Navigate to /wp-content/plugins/tin-canny-learndash-reporting/. Check for the presence of these files: TinCan_Content_List_Table.php, licensing.php, and reporting-admin-menu.php.
    Affected if Any of these three PHP files exist in the plugin directory, indicating the vulnerable code is present.
  3. Review access logs for exploitation attempts
    Examine web server access logs (Apache error.log, Nginx access.log, or WAF logs) for requests to the plugin directory containing the vulnerable GET parameters: search_key, message, tc_filter_group, tc_filter_user, tc_filter_course, tc_filter_lesson, tc_filter_module, tc_filter_action, tc_filter_data_range, or tc_filter_data_range_last.
  4. Check for authenticated admin sessions
    In WordPress admin, go to Users > All Users. Review which users have administrator or editor roles that would have access to the Tin Canny Reporting plugin admin pages.
    Affected if Authenticated users with admin/editor privileges exist in the WordPress installation, providing the attacker context required to exploit the XSS vulnerability.

A user is affected if the Tin Canny LearnDash Reporting plugin version is below 3.4.4 AND the plugin files (TinCan_Content_List_Table.php, licensing.php, reporting-admin-menu.php) are present in the environment.

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

Update the Tin Canny LearnDash Reporting plugin to version 3.4.4 or later, which includes proper input sanitization for the affected GET parameters.

Fix this in Tin Canny Reporting For Learndash Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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