dbcve.org
NetactApplication · Nokia

CVE-2023-26059

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
An issue was discovered in Nokia NetAct before 22 SP1037. On the Site Configuration Tool tab, attackers can upload a ZIP file which, when processed, exploits Stored XSS. The upload option of the Site Configuration tool does not validate the file contents. The application is in a demilitarised zone behind a perimeter firewall and without exposure to the internet. The attack can only be performed by an internal user.

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 confidence

Nokia NetAct's Site Configuration Tool allows users to upload ZIP files without validating the file contents, enabling attackers to embed malicious scripts that execute when the file is processed - a Stored XSS vulnerability.

MitigationImplement strict file content validation (not just extension checking) on the upload function, sanitize any file metadata displayed to users, and apply the vendor patch (SP1037 or later).

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
NetactApplication
Affected:= 20.1

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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 NetAct installation and version
    Check system inventory or run: /opt/nokia/bin/nvGen -V or look for NetAct installation directories (/opt/nokia/netact/) and check version file or banner
    Affected if Nokia NetAct version 20.1 is installed
  2. Locate Site Configuration Tool component
    Navigate to NetAct installation directory and identify the Site Configuration Tool module - typically found under /opt/nokia/netact/sct/ or similar path within the NetAct structure
    Affected if The Site Configuration Tool component exists in the installation
  3. Verify upload functionality is accessible
    Check if the file upload feature in Site Configuration Tool is enabled and accessible to users - look for upload forms or APIs in the web interface or configuration files
    Affected if The upload feature is enabled and exposed to users
  4. Inspect upload validation configuration
    Review configuration files for the upload function in Site Configuration Tool - check for content-type validation, file content inspection, or sanitization settings in XML config files under the SCT module
    Affected if No content validation (only extension checking or no validation) is configured for ZIP file uploads

Your environment is affected if Nokia NetAct version 20.1 is installed with the Site Configuration Tool and its upload feature is accessible without proper content validation on uploaded ZIP files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file content validation (not just extension checking) on the upload function, sanitize any file metadata displayed to users, and apply the vendor patch (SP1037 or later).

Recommended fix Moderate confidence

NetAct 22 SP1037 or later

  1. Contact Nokia customer support to obtain the NetAct 22 SP1037 patch or upgrade package
  2. Review the patch release notes for any specific prerequisites or installation requirements
  3. Back up the current NetAct configuration before applying the patch
  4. Apply the SP1037 patch following Nokia's standard patch deployment procedures
  5. After patching, verify that the Site Configuration Tool properly validates uploaded ZIP file contents
  6. Confirm the XSS vulnerability is remediated by attempting to upload a test file with script content (in a test environment first)
Caveat Review release notes for any compatibility considerations; patches are typically backward compatible but test in non-production first

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

Fix this in Netact Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26059 — 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-2023-26059 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