CVE-2021-35966
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 · uneditedThe specific function of the Orca HCM digital learning platform does not filter input parameters properly, which causing the URL can be redirected to any website. Remote attackers can use the vulnerability to execute phishing attacks.
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 confidenceOrca HCM digital learning platform contains an open redirect vulnerability where the application fails to properly validate input parameters used in URL redirection logic. Attackers can craft malicious URLs with arbitrary external destinations, causing the application to redirect users to attacker-controlled websites for phishing attacks.
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<= 10.0CVSS 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.
-
Identify Orca HCM installationLocate the Learningdigital Orca HCM application in your environment. Check for web applications, services, or systems running the Orca HCM platform.Affected if Orca HCM digital learning platform is deployed in the environment.
-
Determine installed versionCheck the installed version of Orca HCM. This is typically found in application metadata, about pages, or system information. Compare against the affected range: version 10.0 and below.Affected if The installed version is Orca HCM version 10.0 or lower.
-
Identify redirect-enabled parametersReview web application URLs and parameters for common redirect indicators such as 'redirect', 'url', 'next', 'dest', 'target', 'go', or 'return' parameters. Test suspected parameters by supplying an external domain value.Affected if The application accepts user-controlled parameters used in redirect logic.
-
Verify redirect validationAnalyze how the application handles redirect parameters. Submit a test redirect to an external domain (such as example.com) and observe whether the application accepts it or validates it against an allowed list.Affected if The application allows arbitrary external URLs in redirect parameters without strict whitelist validation.
If Orca HCM version 10.0 or below is deployed AND the application uses user-supplied input in redirect parameters without whitelist validation, the environment is affected by this open redirect vulnerability.
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 dataImplement strict whitelist-based validation for redirect URL parameters, ensuring only trusted/internal domains are allowed. Alternatively, avoid using user-supplied input directly in redirects and use a mapping of indirect references to actual URLs.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35966 — 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-2021-35966 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