# CVE-2025-13506: Improper Authorization in Nebim Neyir's Nebim V3 ERP

> Attackers can escalate privileges from the database to control the operating system in Nebim V3 ERP.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 12 Dec 2025
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-7738-gqcf-gx4x

## What is CVE-2025-13506?

CVE-2025-13506 is a high-severity vulnerability in Nebim V3 ERP, published on 12 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Execution with Unnecessary Privileges vulnerability in Nebim Neyir Computer Industry and Services Inc. Nebim V3 ERP allows Expanding Control over the Operating System from the Database.

This issue affects Nebim V3 ERP: from 2.0.59 before 3.0.1.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2025-13506 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13506 is a high-severity vulnerability in Nebim V3 ERP, published on 12 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-13506 in the wild and no public exploit code.

Affected product: Nebim V3 ERP. 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-13506/ (Markdown: https://insights.sbomify.com/CVE-2025-13506/index.md)
```

## Sources

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

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