# CVE-2019-10253: Cross-site request forgery in n/a

> A CSRF vulnerability in TeamMate+ allows remote attackers to upload or replace files by bypassing token validation, potentially compromising application data integrity.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **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:** 9 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-59f2-wmj7-pc4x

## What is CVE-2019-10253?

CVE-2019-10253 is a medium-severity vulnerability in n/a, published on 9 Sep 2019. 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

A Cross-Site Request Forgery (CSRF) vulnerability exists in TeamMate+ 21.0.0.0 that allows a remote attacker to modify application data (upload malicious/forged files on a TeamMate server, or replace existing uploaded files with malicious/forged files). The specific flaw exists within the handling of Upload/DomainObjectDocumentUpload.ashx requests because of failure to validate a CSRF token before handling a POST request.

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

## Which versions are affected by CVE-2019-10253?

It affects 1 product.


Products: Teammatesolutions Teammate\+.

## How do I fix CVE-2019-10253?

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

## Is CVE-2019-10253 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10253 and fix it if it is affected.

What it is: CVE-2019-10253 is a medium-severity vulnerability in n/a, published on 9 Sep 2019. 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-2019-10253 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-2019-10253/ (Markdown: https://insights.sbomify.com/CVE-2019-10253/index.md)
```

## Sources

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

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