# CVE-2025-13129: Business Logic Error in Seneka Software's Onaylarım

> Attackers can misuse functionality due to improper enforcement of behavioral workflows in the Onaylarım approval system.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-96fr-rv8q-2885

## What is CVE-2025-13129?

CVE-2025-13129 is a medium-severity vulnerability in Seneka Software Hardware Information Technology Trade Contracting and Industry Ltd. Co. Onaylarım, published on 1 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Enforcement of Behavioral Workflow vulnerability in Seneka Software Hardware Information Technology Trade Contracting and Industry Ltd. Co. Onaylarım allows Functionality Misuse.

This issue affects Onaylarım: from 25.09.26.01 through 18112025.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow)

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


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

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

## Is CVE-2025-13129 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13129 is a medium-severity vulnerability in Seneka Software Hardware Information Technology Trade Contracting and Industry Ltd. Co. Onaylarım, published on 1 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13129 in the wild and no public exploit code.

Affected product: Seneka Software Hardware Information Technology Trade Contracting and Industry Ltd. Co. Onaylarım. 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-13129/ (Markdown: https://insights.sbomify.com/CVE-2025-13129/index.md)
```

## Sources

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

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