# CVE-2024-6188: Parsec Automation TrackSYS pagedefinition direct request

> Attackers can bypass authorization to access restricted page definitions in Parsec TrackSYS via direct requests, potentially exposing sensitive data.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-c4p5-rq8v-r8c2

## What is CVE-2024-6188?

CVE-2024-6188 is a medium-severity missing authorization vulnerability in Parsec Automation TrackSYS, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Parsec Automation TrackSYS 11.x.x and classified as problematic. This issue affects some unknown processing of the file /TS/export/pagedefinition. The manipulation of the argument ID leads to direct request. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269159. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-425 (Direct Request)

## Which versions are affected by CVE-2024-6188?


## How do I fix CVE-2024-6188?

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

## Is CVE-2024-6188 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6188 exists.

Public exploit code:

- TrakSYS 11.x.x - Sensitive Data Exposure (nuclei): http/cves/2024/CVE-2024-6188.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6188 and fix it if it is affected.

What it is: CVE-2024-6188 is a medium-severity missing authorization vulnerability in Parsec Automation TrackSYS, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6188 exists.

Affected product: Parsec Automation TrackSYS. 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-2024-6188/ (Markdown: https://insights.sbomify.com/CVE-2024-6188/index.md)
```

## Sources

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

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