CVE-2025-24937
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 · uneditedFile contents could be read from the local file system by an attacker. Additionally, malicious code could be inserted in the file, leading to a full compromise of the web application and the container it is running on. The vulnerable component is bound to the network stack and the set of possible attackers extends up to and including the entire Internet. The web application allows arbitrary files to be included in a file that was downloadable and executable by the web server.
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 file inclusion vulnerability (likely local file inclusion) in a network-exposed web application that allows attackers to read arbitrary files from the local filesystem and inject malicious code, leading to remote code execution and complete container compromise.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 if Nokia Wavesuite Noc is installedCheck system for presence of Nokia Wavesuite Noc application files, services, or processes. Look for processes named 'wavesuite' or 'noc' or check installed software listings.Affected if Nokia Wavesuite Noc is present on the system
-
Determine the installed versionCheck the Wavesuite Noc version through its web interface, configuration files, or command-line tools. Common locations include /opt/wavesuite/, /usr/local/wavesuite/, or the application's 'about' or 'status' page.Affected if The installed version matches 23.6, 23.12, or 24.6 exactly
-
Check for network exposure of the web applicationDetermine if the Wavesuite Noc web interface is accessible from the network. Use 'netstat -tlnp' or 'ss -tlnp' to identify listening ports (typically 80, 443, or custom ports) and verify if the service is bound to 0.0.0.0 or an external IP.Affected if The web application is exposed to untrusted networks without proper network segmentation or authentication
-
Inspect web access logs for file inclusion patternsReview web server access logs (typically found in /var/log/, /opt/wavesuite/logs/, or the application logs directory) for suspicious requests containing path traversal sequences such as '../', '..\', or absolute paths like '/etc/passwd'.Affected if Logs contain requests with path traversal patterns targeting sensitive system files
-
Check for unauthorized file access or modificationExamine application logs, system audit logs, and web root directories for unexpected files, modified configurations, or evidence of code injection. Look for new or modified scripts in web-accessible directories.Affected if Evidence exists of arbitrary file reads, unexpected files in web directories, or modified configuration files
You are affected if Nokia Wavesuite Noc versions 23.6, 23.12, or 24.6 are installed AND the web interface is network-accessible, as this enables the file inclusion vulnerability to be exploited.
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.
From vendor dataImplement strict input validation with allowlist approach for file inclusion parameters, restrict file paths to expected directories, and ensure the web server runs with minimal necessary permissions.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24937 — 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-24937 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