dbcve.org
Mantaray NmApplication · Nokia

CVE-2025-24818

HIGH · 8.0 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 25r1-nm or later.
See remediation →
82/100
Remediation priority · High
Zero-click

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 · unedited
Nokia MantaRay NM is vulnerable to an OS command injection vulnerability due to improper neutralization of special elements used in an OS command in Log Search application.

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 confidence

Nokia MantaRay Network Manager contains an OS command injection vulnerability in its Log Search application. The vulnerability stems from improper neutralization of special elements in user-supplied input, allowing authenticated attackers to inject and execute arbitrary operating system commands.

MitigationApply the vendor-provided patch when released. Until then, restrict access to the Log Search functionality to trusted users only and implement strict input validation on all user-provided data before passing it to system calls.

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
Mantaray NmApplication
Affected:< 25r1-nm

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nokia MantaRay Network Manager installation
    Look for MantaRay Nm installation directories, services, or web interfaces. Check system processes for 'mantaray' or 'nm' processes. Look for port 8080, 8443, or common web service ports running Nokia network management applications.
    Affected if No MantaRay Nm installation is found, the system is not affected by this CVE.
  2. Determine installed MantaRay Nm version
    Check the installed version through the web interface (usually in About/Help section), or via command line if available: look for version files in installation directories, check service banner, or consult /opt/nm version files if they exist. Compare against the affected range: versions < 25r1-nm are vulnerable.
    Affected if Installed version is 25r1-nm or higher - NOT vulnerable. Version is below 25r1-nm - VULNERABLE.
  3. Verify Log Search application is enabled
    Check if the Log Search feature is accessible and enabled in the MantaRay web interface. Look for Log Search or logging-related menu items. Review configuration files in the Nm installation directory for Log Search module settings.
    Affected if Log Search is disabled or not present, the command injection cannot be exploited even on vulnerable versions.
  4. Assess access controls on Log Search
    Review user access controls, roles, and permissions within MantaRay Nm. Determine if untrusted or low-privilege users can access the Log Search functionality. Check authentication configuration and user group assignments.
    Affected if Log Search is accessible to untrusted or low-privilege authenticated users - HIGH RISK for exploitation on vulnerable versions.

System is affected if Nokia MantaRay Nm version is below 25r1-nm AND the Log Search feature is enabled and accessible to the attacking user.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 25r1-nm or later
Fixed in 25r1-nm
Interim mitigation

Apply the vendor-provided patch when released. Until then, restrict access to the Log Search functionality to trusted users only and implement strict input validation on all user-provided data before passing it to system calls.

Recommended fix Moderate confidence

25r1-nm

  1. 1. Backup current MantaRay NM configuration and data
  2. 2. Obtain the fixed version (25r1-nm or later) from Nokia's official support channels
  3. 3. Follow Nokia's standard upgrade procedure for MantaRay NM
  4. 4. After upgrade, verify the Log Search application functions correctly
  5. 5. Confirm the vulnerability is resolved by testing Log Search functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mantaray Nm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24818 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24818 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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