CVE-2023-26062
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a privilege escalation vulnerability in Nokia Web Element Manager where an authenticated, unprivileged user can execute administrative functions due to broken access controls. The vulnerability exists in versions prior to 22 R1 and allows users with standard credentials to perform privileged operations they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 22r1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Nokia Web Element Manager installationLocate the Nokia Web Element Manager installation directory or check for the web application on the system. Common locations include /opt/nokia/wem or C:\Program Files\Nokia\wem. Check for the presence of wem-server or web element manager processes running.Affected if The software is installed and running on the system.
-
Determine installed versionLocate the version information file or check the product about page in the web interface. Typically found in installation_directory/version or accessible via the Help > About menu in the web GUI.Affected if The version is identified as anything prior to 22 R1 (for example, 21.x, 20.x, or earlier releases).
-
Verify standard user accounts existCheck the user management section of the web interface or examine the user configuration database/file. Look for accounts that are NOT assigned administrator or superuser roles.Affected if There are authenticated standard (non-privileged) user accounts configured in the system.
-
Confirm web interface accessibilityVerify that the Nokia Web Element Manager web interface is reachable on the expected port (commonly 443 or 8443). Attempt to access the login page from the management network.Affected if The web interface is accessible and accepts authentication.
If Nokia Web Element Manager is installed with a version prior to 22 R1 and standard user accounts exist with access to the web interface, the environment is likely affected by this privilege escalation vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped22r1
Upgrade Nokia Web Element Manager to version 22 R1 or later to obtain the patch. Since exploitation is only possible from the internal BTS management network, ensure proper network segmentation and access controls are maintained on that management segment.
22 R1
- Identify the current version of Nokia Web Element Manager in use
- Plan an upgrade to version 22 R1 or later
- Schedule a maintenance window for the upgrade
- Follow Nokia's official upgrade procedures to upgrade Web Element Manager to version 22 R1
- After upgrade, verify that unprivileged users can no longer execute administrative functions
- Confirm normal operation of the Web Element Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-26062 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data