Uncanny Toolkit For LearndashWordPress extension · Uncannyowl
CVE-2023-34020
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in Uncanny Owl Uncanny Toolkit for LearnDash.This issue affects Uncanny Toolkit for LearnDash: from n/a through 3.6.4.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 confidenceAn open redirect vulnerability in the Uncanny Owl Uncanny Toolkit for LearnDash WordPress plugin allows attackers to craft malicious URLs that redirect users to untrusted external sites. The vulnerability exists in versions through 3.6.4.3 and stems from improper validation of redirect parameters. With a CVSS score of 6.1, this network-exploitable issue requires low-privilege authentication and user interaction.
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 Toolkit For LearndashWordPress extension
<= 3.6.4.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Uncanny Toolkit for LearnDash' or check the plugin directory /wp-content/plugins/uncanny-learndash-toolkit/Affected if The plugin is present in the WordPress installation
-
Identify installed versionIn WordPress admin_plugins list, the version number is displayed next to the plugin name, or inspect the main plugin file header in /wp-content/plugins/uncanny-learndash-toolkit/Affected if Version listed is 3.6.4.3 or lower
-
Check for redirect-enabled featuresReview plugin settings for any redirect-related options or shortcodes that handle URL redirection, typically found in plugin settings pages under LearnDash or Toolkit configurationAffected if Redirect functionality is enabled or accessible to users
-
Audit outgoing redirect parametersInspect HTTP traffic or server logs for requests to the site that contain redirect parameters (such as redirect_to, url, destination, or similar) pointing to the plugin's endpointsAffected if Redirect parameters are being processed by the plugin without strict domain validation
Environment is affected if Uncanny Toolkit for LearnDash version 3.6.4.3 or lower is installed and the plugin's redirect functionality is accessible to low-privilege users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Uncanny Toolkit for LearnDash to the latest version and implement strict validation ensuring all redirect parameters point only to trusted, internal domains.
Fix this in Uncanny Toolkit For Learndash
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34020 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34020 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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