CVE-2026-3007
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 · uneditedSuccessful exploitation of the stored cross-site scripting (XSS) vulnerability could allow an attacker to execute arbitrary JavaScript on any user account that has access to Koollab LMS’ courselet feature.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in Koollab LMS within the courselet feature. The vulnerability allows attackers to inject malicious JavaScript that persists in the application and executes when other users access the affected courselet functionality.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 if Koollab LMS is installedSearch the system for Koollab LMS application files, or check web server document roots for 'koollab' or 'koolab' directory structures. If using a package manager, look for installed packages related to Koollab.Affected if Koollab LMS is present on the system
-
Determine the installed version of Koollab LMSCheck version files in the Koollab installation directory (such as version.php, composer.json, package.json, or a README file). Compare the found version against any known vulnerable version ranges for CVE-2026-3007.Affected if The installed version falls within the vulnerable version range for this CVE
-
Verify the courselet feature is accessibleLocate the courselet module within the Koollab LMS application structure. Determine if the feature is enabled and accessible to users (check configuration files, database records for active courselets, or navigate to courselet-related URLs if the application is running).Affected if The courselet feature is enabled and accessible to users
-
Inspect courselet input fields for sanitizationIf the application is running, access the courselet creation/editing functionality and examine the input fields where user-supplied data is entered. Look for evidence that HTML/script characters are being filtered, escaped, or encoded before storage. Check application source code in the courselet controller/model files for input validation routines.Affected if User input in courselet fields is stored and displayed without proper output encoding or input validation (the vulnerability is present)
A user is affected if Koollab LMS is installed with a vulnerable version and the courselet feature is accessible and processes user input without sanitization, allowing stored XSS to persist and execute for other 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 dataImplement proper input validation and output encoding for all user-supplied data in the courselet feature. Consider deploying Content Security Policy (CSP) headers as an additional defense-in-depth measure.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3007 — 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-3007 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