dbcve.org
Coursemill Learning Management SystemApplication · Trivantis

CVE-2013-3601

MEDIUM · 6.0 CVSS v2.0 Published 2013-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Coursemill Learning Management System (LMS) 6.6 does not properly restrict JSP function calls, which allows remote authenticated users to perform arbitrary JSP operations by leveraging the Student role and providing an op parameter.

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 confidence

Coursemill LMS 6.6 fails to properly restrict JSP function calls based on user role, allowing authenticated users with only Student privileges to execute arbitrary JSP operations via a manipulated 'op' parameter. This represents a privilege escalation vulnerability where the application does not enforce role-based access controls on certain functionality.

MitigationRestrict the 'op' parameter and related JSP function calls to only permitted user roles, implementing proper server-side authorization checks before executing any privileged operations regardless of parameter values provided by the client.

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
Coursemill Learning Management SystemApplication
Affected:= 6.6

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
M
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:S/C:P/I:P/A:P

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. Confirm Coursemill LMS installation
    Look for Coursemill web application files in your web server's deployment directory (e.g., Tomcat webapps, IIS inetpub, or WebSphere apps). Search for directories or WAR files named 'coursemill' or 'Coursemill'. Check your application server's management console for deployed applications matching this name.
    Affected if Coursemill LMS is deployed on the server and accessible as a web application.
  2. Identify installed version
    Navigate to the Coursemill admin or about page (typically /coursemill/about.html, /coursemill/admin/about.jsp, or check version.txt in the installation directory). Alternatively, examine the coursemill JAR or WAR file's manifest file for the version attribute.
    Affected if The installed version is exactly 6.6.
  3. Locate vulnerable JSP components
    Search the Coursemill deployment directory for JSP files that accept an 'op' parameter, particularly in admin or privileged function areas. Common paths may include /coursemill/admin/, /coursemill/common/, or similar. Look for JSP files handling operations like user management, content administration, or system configuration.
    Affected if JSP files accepting the 'op' parameter exist and are accessible without proper role validation.
  4. Test role enforcement on JSP operations
    Using a browser or HTTP tool, authenticate as a Student-level user. Attempt to access known admin JSP operations by manipulating the 'op' parameter (e.g., op=editUser, op=manageContent). Check if the application returns admin functionality or privileged operations without rejecting the request based on role.
    Affected if Student-role users can access privileged JSP operations by manipulating the 'op' parameter.

You are affected if Coursemill LMS version 6.6 is installed and the application allows authenticated Student-role users to access privileged JSP operations through the 'op' parameter without proper server-side role validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict the 'op' parameter and related JSP function calls to only permitted user roles, implementing proper server-side authorization checks before executing any privileged operations regardless of parameter values provided by the client.

Fix this in Coursemill Learning Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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