# CVE-2020-24983: Cross-site request forgery in n/a

> An unauthenticated attacker can trick an admin into changing dashboard names via CSRF, requiring user interaction to modify application data.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 11 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mfjv-v3p5-r7fc

## What is CVE-2020-24983?

CVE-2020-24983 is a high-severity vulnerability in n/a, published on 11 Mar 2021. 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

An issue was discovered in Quadbase EspressReports ES 7 Update 9. An unauthenticated attacker can create a malicious HTML file that houses a POST request made to the DashboardBuilder within the target web application. This request will utilise the target admin session and perform the authenticated request (to change the Dashboard name) as if the victim had done so themselves, aka CSRF.

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

## Which versions are affected by CVE-2020-24983?

It affects 1 product.


Products: Quadbase Espressreports Es.

## How do I fix CVE-2020-24983?

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

## Is CVE-2020-24983 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-24984](https://insights.sbomify.com/CVE-2020-24984/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24983 and fix it if it is affected.

What it is: CVE-2020-24983 is a high-severity vulnerability in n/a, published on 11 Mar 2021. 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-2020-24983 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-2020-24983/ (Markdown: https://insights.sbomify.com/CVE-2020-24983/index.md)
```

## Sources

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

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