# CVE-2017-3187: The dotCMS administration panel, versions 3.7.1 and earlier, are vulnerable to cross-site request forgery

> An attacker can trick an authenticated administrator into executing arbitrary system commands or actions via cross-site request forgery in the dotCMS administration panel.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wcqw-wpq6-v3g4

## What is CVE-2017-3187?

CVE-2017-3187 is a high-severity vulnerability in Dotcms Dotcms, published on 24 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The dotCMS administration panel, versions 3.7.1 and earlier, are vulnerable to cross-site request forgery. The dotCMS administrator panel contains a cross-site request forgery (CSRF) vulnerability. An attacker can perform actions with the same permissions as a victim user, provided the victim has an active session and is induced to trigger the malicious request. An unauthenticated remote attacker may perform actions with the dotCMS administrator panel with the same permissions of a victim user or execute arbitrary system commands with the permissions of the user running the dotCMS application.

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

## Which versions are affected by CVE-2017-3187?

It affects 1 product.


Products: Dotcms Dotcms.

## How do I fix CVE-2017-3187?

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

## Is CVE-2017-3187 being exploited?

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

## Other vulnerabilities in Dotcms Dotcms

- [CVE-2022-26352](https://insights.sbomify.com/CVE-2022-26352/): dotCMS Unrestricted Upload of File (critical 9.8, exploited in the wild)
- [CVE-2020-19138](https://insights.sbomify.com/CVE-2020-19138/): File upload in n/a (critical 9.8)
- [CVE-2020-6754](https://insights.sbomify.com/CVE-2020-6754/): Path traversal in n/a (critical 9.8)
- [CVE-2017-5344](https://insights.sbomify.com/CVE-2017-5344/): SQL injection in n/a (critical 9.8)
- [CVE-2016-2355](https://insights.sbomify.com/CVE-2016-2355/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3187 and fix it if it is affected.

What it is: CVE-2017-3187 is a high-severity vulnerability in Dotcms Dotcms, published on 24 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-3187 in the wild and no public exploit code.

Affected product: Dotcms Dotcms. 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-2017-3187/ (Markdown: https://insights.sbomify.com/CVE-2017-3187/index.md)
```

## Sources

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

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