# CVE-2020-24898: Server-side request forgery in n/a

> An attacker can exploit a Server-Side Request Forgery vulnerability in the Table Filter and Charts plugin for Confluence Server to access internal resources.

- **Severity:** High 7.6 (`CVSS:3.1/AC:L/AV:N/A:L/C:H/I:L/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6wvg-x4mx-rm6h

## What is CVE-2020-24898?

CVE-2020-24898 is a high-severity server-side request forgery vulnerability in n/a, published on 29 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Table Filter and Charts for Confluence Server app before 5.3.26 (for Atlassian Confluence) allows SSRF via the "Table from CSV" macro (URL parameter).

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Stiltsoft Table Filter and Charts for Confluence Server.

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

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

## Is CVE-2020-24898 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-24897](https://insights.sbomify.com/CVE-2020-24897/): Cross-site scripting in n/a (high 8.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24898 is a high-severity server-side request forgery vulnerability in n/a, published on 29 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-24898 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-24898/ (Markdown: https://insights.sbomify.com/CVE-2020-24898/index.md)
```

## Sources

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

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