dbcve.org
NetactApplication · Nokia

CVE-2023-26060

HIGH · 8.8 CVSS v3.1 Published 2023-04-24
Fix available
A fix is available. Upgrade to 20.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An issue was discovered in Nokia NetAct before 22 FP2211. On the Working Set Manager page, users can create a Working Set with a name that has a client-side template injection payload. Input validation is missing during creation of the working set. For an external attacker, it is very difficult to exploit this, because a few dynamically created parameters such as Jsession-id, a CSRF token, and an Nxsrf token would be needed. The attack can realistically 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

Client-side template injection in Nokia NetAct's Working Set Manager allows malicious payloads to be injected via the Working Set name field during creation due to missing input validation. This manifests as stored XSS and requires authentication along with multiple security tokens (JSession-id, CSRF token, Nxsrf token), making realistic exploitation limited to internal users.

MitigationImplement strict input validation with allowlist filtering and proper output encoding on the Working Set name parameter to neutralize template injection payloads before storage or rendering.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Confirm Nokia NetAct product and version
    Locate the installed Nokia NetAct version in the system documentation, about page, or software inventory. Compare it against the affected range: versions below 20.1.
    Affected if The installed version is Nokia NetAct and is lower than 20.1.
  2. Verify Working Set Manager is accessible
    Log into the NetAct web interface and navigate to the Working Set Manager module. Confirm the feature is present and functional.
    Affected if Working Set Manager module is available and accessible in the NetAct interface.
  3. Check authentication state
    Inspect the active session by examining browser cookies or HTTP headers for JSession-id, CSRF token, and Nxsrf token presence after logging in.
    Affected if You can authenticate to NetAct and obtain all three security tokens (JSession-id, CSRF token, Nxsrf token).
  4. Inspect existing Working Set names for injection artifacts
    In the Working Set Manager interface, list all existing Working Sets and examine the names stored in the Working Set name field for any unsanitized HTML, script, or template syntax characters.
    Affected if Any Working Set name contains raw HTML tags, script elements, or template injection syntax that renders in the browser without encoding.
  5. Test Working Set name field for input validation
    Create a new Working Set and input a test payload containing non-alphanumeric characters (such as <script>alert(1)</script> or {{constructor}}). Save it and observe whether the payload is stored and rendered as-is or properly encoded.
    Affected if The test payload is stored and rendered literally in the browser without encoding or rejection, indicating missing input validation.

You are affected if Nokia NetAct version is below 20.1, the Working Set Manager is accessible, and the Working Set name field accepts and stores unsanitized input that renders as executable code in the browser.

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 20.1 or later
Fixed in 20.1
Interim mitigation

Implement strict input validation with allowlist filtering and proper output encoding on the Working Set name parameter to neutralize template injection payloads before storage or rendering.

Recommended fix Moderate confidence

Nokia NetAct 22 FP2211 or later

  1. 1. Identify the current Nokia NetAct version running in the environment
  2. 2. Upgrade to Nokia NetAct version 22 FP2211 or later release
  3. 3. Verify the upgrade was successful by checking the NetAct version information
  4. 4. Test the Working Set Manager functionality to confirm normal operation

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

Fix this in Netact Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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