CVE-2025-24938
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 · uneditedThe web application allows user input to pass unfiltered to a command executed on the underlying operating system. An attacker with high privileged access (administrator) to the application has the potential execute commands on the operating system under the context of the webserver. The vulnerable component is bound to the network stack and the set of possible attackers extends up to and including the entire Internet. Has the potential to inject command while creating a new User from User Management.
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 · high confidenceThis is an OS command injection vulnerability in the web application's User Management module. When creating a new user, the application passes administrator-supplied input directly to an operating system command without sanitization, allowing arbitrary command execution under the webserver's privileges.
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= 23.6= 23.12= 24.6CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/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 Wavesuite Noc versionLocate the installed version of Nokia Wavesuite Noc in the system documentation, software inventory, or application about page. Check the application binaries or deployment configuration files for version information.Affected if The installed version matches exactly 23.6, 23.12, or 24.6
-
Confirm User Management function is accessibleVerify that the User Management module or function is enabled and accessible in the Wavesuite Noc web interface. Log into the application and navigate to the user creation or administration section.Affected if The User Management feature is enabled and operational in the web application
-
Inspect user creation endpointReview the web application configuration or access logs for the user creation functionality. Identify the backend handler or API endpoint responsible for processing new user requests.Affected if The application processes user creation requests through a backend that interacts with the operating system
-
Check webserver user contextDetermine the operating system user account under which the web application or application server runs. Review process listings or service configurations.Affected if The webserver runs with elevated privileges or privileges that could allow command execution beyond intended scope
A user is affected if their Nokia Wavesuite Noc installation is version 23.6, 23.12, or 24.6 AND the User Management function is accessible, as the vulnerability allows OS command injection during user creation.
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 · scopedImplement strict input validation with allow-lists and refactor code to avoid constructing OS commands from user input; if OS commands are unavoidable, use parameterized methods or existing libraries rather than shell execution.
24.12 or later stable release
- 1. Obtain the latest stable release of Wavesuite Noc from Nokia's official support channels (www.nokia.com)
- 2. Review the release notes for version 24.12 or later to confirm inclusion of the CVE-2025-24938 security fix
- 3. Create a full backup of the current Wavesuite Noc configuration and database
- 4. Schedule a maintenance window as the upgrade may require service interruption
- 5. Execute the upgrade following the official Nokia upgrade documentation
- 6. Verify the upgrade was successful by logging into the web interface
- 7. Test the User Management functionality to ensure normal operation after upgrade
- 8. Confirm the underlying OS no longer accepts command injection via the user creation endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24938 — 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-2025-24938 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