# CVE-2018-18696: Cross-site request forgery in n/a

> Cross-site request forgery in MicroStrategy Analytics allows attackers to trick users into performing unintended actions, requiring configuration changes to mitigate.

- **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:** 28 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4rv4-2rhp-3qjw

## What is CVE-2018-18696?

CVE-2018-18696 is a high-severity vulnerability in n/a, published on 28 Dec 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

main.aspx in Microstrategy Analytics 10.4.0026.0049 and earlier has CSRF. NOTE: The vendor claims that documentation for preventing a CSRF attack has been provided (https://community.microstrategy.com/s/article/KB37643-New-security-feature-introduced-in-MicroStrategy-Web-9-0?language=en_US) and disagrees that this issue is a vulnerability. They also claim that MicroStrategy was never properly informed of this issue via normal support channels or their vulnerability reporting page on their website, so they were unable to evaluate the report or explain how this is something their customers view as a feature and not a security vulnerability

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

## Which versions are affected by CVE-2018-18696?

It affects 1 product.


Products: Microstrategy Microstrategy.

## How do I fix CVE-2018-18696?

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

## Is CVE-2018-18696 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-24815](https://insights.sbomify.com/CVE-2020-24815/): Server-side request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18696 and fix it if it is affected.

What it is: CVE-2018-18696 is a high-severity vulnerability in n/a, published on 28 Dec 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-2018-18696 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-2018-18696/ (Markdown: https://insights.sbomify.com/CVE-2018-18696/index.md)
```

## Sources

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

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