# CVE-2023-2958: IDOR in ATS Pro

> Attackers can bypass authentication and access unauthorized data in Origin Software ATS Pro due to insecure direct object references.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2023
- **Updated:** 22 May 2026
- **Also known as:** GHSA-84c8-qpcc-7wf9

## What is CVE-2023-2958?

CVE-2023-2958 is a critical missing authorization vulnerability in Origin Software ATS Pro, published on 17 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authorization Bypass Through User-Controlled Key vulnerability in Origin Software ATS Pro allows Authentication Abuse, Authentication Bypass.

This issue affects ATS Pro: before 20230714.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Orjinyazilim Ats Pro.

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

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

## Is CVE-2023-2958 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2958 is a critical missing authorization vulnerability in Origin Software ATS Pro, published on 17 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-2958 in the wild and no public exploit code.

Affected product: Origin Software ATS Pro. 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-2958/ (Markdown: https://insights.sbomify.com/CVE-2023-2958/index.md)
```

## Sources

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

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