# CVE-2025-56015: GenieACS has an unauthenticated access vulnerability via the NBI API endpoint

> Unauthenticated attackers can access the GenieACS NBI API endpoint, bypassing authorization controls to potentially read sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-2h6j-mhcp-9j9h

## What is CVE-2025-56015?

CVE-2025-56015 is a high-severity missing authorization vulnerability in n/a, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In GenieACS 1.2.13, an unauthenticated access vulnerability exists in the NBI API endpoint.

Weakness: CWE-284 (Improper Access Control)

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

2 open source packages ship an affected version, including genieacs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `genieacs` | npm | All versions | None |
| `genieacs` | npm | All versions | None |

Products: Genieacs Genieacs.

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

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

## Is CVE-2025-56015 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56015 exists.

Public exploit code:

- https://github.com/e1st/CVE-2025-56015 (github_poc): https://github.com/e1st/CVE-2025-56015

## Other vulnerabilities in n/a

- [CVE-2021-46704](https://insights.sbomify.com/CVE-2021-46704/): OS Command Injection in GenieACS (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56015 is a high-severity missing authorization vulnerability in n/a, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56015 exists.

Affected packages and fixed versions:
- genieacs (npm): affected all versions; no fix listed
- genieacs (npm): affected all versions; no fix listed

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-56015/ (Markdown: https://insights.sbomify.com/CVE-2025-56015/index.md)
```

## Sources

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

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