# CVE-2023-26062: Privilege escalation in n/a

> An authenticated unprivileged user can execute administrative functions in Nokia Web Element Manager, requiring access to the internal management network.

- **Severity:** High 7.0 (`CVSS:3.1/AC:H/AV:L/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2023
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-gh5j-gp96-cg99

## What is CVE-2023-26062?

CVE-2023-26062 is a high-severity vulnerability in n/a, published on 14 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A mobile network solution internal fault is found in Nokia Web Element Manager before 22 R1, in which an authenticated, unprivileged user can execute administrative functions. Exploitation is not possible from outside of mobile network solution architecture. This means that exploit is not possible from mobile network user UEs, from roaming networks, or from the Internet. Exploitation is possible only from a CSP (Communication Service Provider) mobile network solution internal BTS management network.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2023-26062?

It affects 1 product.


Products: Nokia Web Element Manager.

## How do I fix CVE-2023-26062?

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

## Is CVE-2023-26062 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26062 and fix it if it is affected.

What it is: CVE-2023-26062 is a high-severity vulnerability in n/a, published on 14 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-26062 in the wild and no public exploit code.

Affected product: n/a. 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-2023-26062/ (Markdown: https://insights.sbomify.com/CVE-2023-26062/index.md)
```

## Sources

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

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