# CVE-2025-1161: Improper Authorization in Nomysoft Informatics' Nomysem

> Attackers can escalate privileges in Nomysem due to improper use of privileged APIs, potentially gaining unauthorized access to higher-level functions.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-f274-2846-89q3

## What is CVE-2025-1161?

CVE-2025-1161 is a high-severity vulnerability in NomySoft Information Technology Training and Consulting Inc. Nomysem, published on 10 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Incorrect Use of Privileged APIs vulnerability in NomySoft Information Technology Training and Consulting Inc. Nomysem allows Privilege Escalation.

This issue affects Nomysem: through May 2025.

Weakness: CWE-648 (Incorrect Use of Privileged APIs)

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


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

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

## Is CVE-2025-1161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1161 is a high-severity vulnerability in NomySoft Information Technology Training and Consulting Inc. Nomysem, published on 10 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-1161 in the wild and no public exploit code.

Affected product: NomySoft Information Technology Training and Consulting Inc. Nomysem. 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-1161/ (Markdown: https://insights.sbomify.com/CVE-2025-1161/index.md)
```

## Sources

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

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