# CVE-2023-47024: Cross-site request forgery in n/a

> A CSRF vulnerability in NCR Terminal Handler allows attackers to perform one-click account takeover by exploiting weak security controls in the WSDL.

- **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:** 20 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-6g2q-qmv9-573f

## What is CVE-2023-47024?

CVE-2023-47024 is a high-severity vulnerability in n/a, published on 20 Jan 2024. 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

Cross-Site Request Forgery (CSRF) in NCR Terminal Handler v.1.5.1 leads to a one-click account takeover. This is achieved by exploiting multiple vulnerabilities, including an undisclosed function in the WSDL that has weak security controls and can accept custom content types.

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

## Which versions are affected by CVE-2023-47024?

It affects 1 product.


Products: Ncratleos Terminal Handler.

## How do I fix CVE-2023-47024?

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

## Is CVE-2023-47024 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47024 and fix it if it is affected.

What it is: CVE-2023-47024 is a high-severity vulnerability in n/a, published on 20 Jan 2024. 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-2023-47024 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-2023-47024/ (Markdown: https://insights.sbomify.com/CVE-2023-47024/index.md)
```

## Sources

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

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