CVE-2026-56877
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 SCORM lab launch endpoint in Skillable (scorm.skillable.com) through 2026-07-13 does not validate the client-supplied userId parameter against the authenticated SCORM session token. An authenticated user can substitute arbitrary userId values to bypass per-user lab launch rate limits and consume other users' lab allocations, resulting in denial of service against targeted users' lab and exam access. Skillable was formerly named Learn on Demand Systems.
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 confidenceThe SCORM lab launch endpoint in Skillable (scorm.skillable.com) does not validate that the client-supplied userId parameter matches the authenticated user's session token. This allows any authenticated user to specify arbitrary userId values, bypassing rate limits intended to restrict lab launches per user and enabling consumption of other users' lab allocations, causing denial of service against targeted users' lab and exam access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 you use the affected Skillable SCORM serviceCheck if your applications or integrations connect to scorm.skillable.com for lab or exam launchesAffected if Your environment makes requests to scorm.skillable.com for SCORM lab launches
-
Identify the SCORM lab launch endpointReview your application network traffic or API documentation to locate the endpoint that handles lab launches and accepts a userId parameterAffected if Your launch requests include a userId parameter that can be controlled
-
Test userId parameter manipulationAuthenticate as one user, then send a lab launch request with a different userId value in the request (different from your authenticated session's user)Affected if The system accepts a userId that does not match your authenticated session token and returns a successful lab launch response
-
Verify rate limit bypassSend multiple lab launch requests with varying userId values and observe whether rate limits apply per-session or per-client-supplied userIdAffected if Rate limits are enforced based on the client-supplied userId rather than the authenticated session, allowing unlimited launches across different userIds
-
Check lab allocation consumptionLaunch labs using arbitrary userId values and monitor whether the targeted users' lab allocation balances decrease without their knowledgeAffected if Lab allocations are consumed from the userId specified in the request rather than from the authenticated user's allocation
You are affected if your environment uses scorm.skillable.com and the lab launch endpoint accepts a client-supplied userId that bypasses session-based validation and rate limiting.
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 server-side validation to ensure the userId parameter matches the authenticated user's identity from the session token, and enforce strict rate limiting tied to authenticated sessions rather than client-supplied values.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56877 — 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-2026-56877 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