dbcve.org
Uncanny Groups For LearndashApplication · Uncannyowl

CVE-2020-35650

MEDIUM · 6.1 CVSS v3.1 Published 2020-12-23
Fix available
A fix is available. Upgrade to 3.7 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 Groups for LearnDash before v3.7 allow authenticated remote attackers to inject arbitrary JavaScript or HTML via the ulgm_code_redeem POST Parameter in user-code-redemption.php, the ulgm_user_first POST Parameter in user-registration-form.php, the ulgm_user_last POST Parameter in user-registration-form.php, the ulgm_user_email POST Parameter in user-registration-form.php, the ulgm_code_registration POST Parameter in user-registration-form.php, the ulgm_terms_conditions POST Parameter in user-registration-form.php, the _ulgm_total_seats POST Parameter in frontend-uo_groups_buy_courses.php, the uncanny_group_signup_user_first POST Parameter in group-registration-form.php, the uncanny_group_signup_user_last POST Parameter in group-registration-form.php, the uncanny_group_signup_user_login POST Parameter in group-registration-form.php, the uncanny_group_signup_user_email POST Parameter in group-registration-form.php, the success-invited GET Parameter in frontend-uo_groups.php, the bulk-errors GET Parameter in frontend-uo_groups.php, or the message GET Parameter in frontend-uo_groups.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 stored cross-site scripting (XSS) vulnerabilities in Uncanny Groups for LearnDash WordPress plugin versions before 3.7 allow authenticated users to inject arbitrary JavaScript/HTML via 15+ vulnerable POST and GET parameters across user-code-redemption.php, user-registration-form.php, frontend-uo_groups_buy_courses.php, group-registration-form.php, and frontend-uo_groups.php.

MitigationUpgrade Uncanny Groups for LearnDash to version 3.7 or later which contains the patched sanitization for all listed 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
Uncanny Groups For LearndashApplication
Affected:< 3.7

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
    Navigate to WordPress admin > Plugins and locate 'Uncanny Groups for LearnDash' by Uncannyowl, or check the plugin directory /wp-content/plugins/uncanny-groups-for-learndash/ for existence
    Affected if Plugin is installed and present in the WordPress environment
  2. Check installed version
    In WordPress admin > Plugins, find the plugin and view the version number under the plugin name, or read version from the plugin's main PHP file header
    Affected if Version number is less than 3.7 (e.g., 3.6.x, 3.5.x, etc.)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the plugin status shows as 'Active'
    Affected if Plugin is enabled and running on the site
  4. Identify user access to vulnerable endpoints
    Review which user roles have access to the affected files: user-code-redemption.php, user-registration-form.php, frontend-uo_groups_buy_courses.php, group-registration-form.php, frontend-uo_groups.php. These are accessed via frontend forms.
    Affected if Any authenticated user role (subscriber, student, member) can access and submit forms via these endpoints

Environment is affected if Uncanny Groups for LearnDash plugin is installed, active, and running version 3.6 or lower, allowing authenticated users to access the vulnerable frontend registration and redemption forms.

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

Upgrade Uncanny Groups for LearnDash to version 3.7 or later which contains the patched sanitization for all listed parameters.

Fix this in Uncanny Groups For Learndash Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,340
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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