# CVE-2013-3605: Cross-site request forgery in n/a

> Remote attackers can hijack user authentication in Coursemill LMS via CSRF, requiring user interaction to execute malicious actions.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Sep 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-65wj-m2q5-xvwq

## What is CVE-2013-3605?

CVE-2013-3605 is a medium-severity vulnerability in n/a, published on 6 Sep 2013. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in Coursemill Learning Management System (LMS) 6.6 allows remote attackers to hijack the authentication of arbitrary users via vectors related to cookies.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2013-3605?

It affects 1 product.


Products: Trivantis Coursemill Learning Management System.

## How do I fix CVE-2013-3605?

No fix has been published for CVE-2013-3605 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-3605 being exploited?

There is no known exploitation of CVE-2013-3605 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-3599](https://insights.sbomify.com/CVE-2013-3599/): Privilege escalation in n/a (critical 9.3)
- [CVE-2013-3600](https://insights.sbomify.com/CVE-2013-3600/): Privilege escalation in n/a (high 8.5)
- [CVE-2013-3602](https://insights.sbomify.com/CVE-2013-3602/): SQL injection in n/a (high 7.5)
- [CVE-2013-5708](https://insights.sbomify.com/CVE-2013-5708/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-3601](https://insights.sbomify.com/CVE-2013-3601/): Code injection in n/a (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3605 and fix it if it is affected.

What it is: CVE-2013-3605 is a medium-severity vulnerability in n/a, published on 6 Sep 2013. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-3605 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-3605/ (Markdown: https://insights.sbomify.com/CVE-2013-3605/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3605
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3605
- OSV: https://osv.dev/vulnerability/CVE-2013-3605

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-3605/
Summaries are generated and may contain mistakes; the official description above is the record.