# CVE-2025-29997: Improper Access Control Vulnerability in CAP back office application

> An authenticated attacker can manipulate API URLs to bypass authorization checks and access other user accounts in the CAP back office application.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/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:** 13 Mar 2025
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-69gq-6xvx-r4vv

## What is CVE-2025-29997?

CVE-2025-29997 is a high-severity missing authorization vulnerability in Rising Technosoft CAP back office application, published on 13 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability exists in the CAP back office application due to improper authorization checks on certain API endpoints. An authenticated remote attacker could exploit this vulnerability by manipulating API request URL to gain unauthorized access to other user accounts.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-29997?


## How do I fix CVE-2025-29997?

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

## Is CVE-2025-29997 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-29997 and fix it if it is affected.

What it is: CVE-2025-29997 is a high-severity missing authorization vulnerability in Rising Technosoft CAP back office application, published on 13 Mar 2025. 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-2025-29997 in the wild and no public exploit code.

Affected product: Rising Technosoft CAP back office application. 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-2025-29997/ (Markdown: https://insights.sbomify.com/CVE-2025-29997/index.md)
```

## Sources

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

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