CVE-2023-26061
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 · uneditedAn issue was discovered in Nokia NetAct before 22 FP2211. On the Scheduled Search tab under the Alarm Reports Dashboard page, users can create a script to inject XSS. Input validation was missing during creation of a scheduled task. 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 confidenceA stored XSS vulnerability exists in Nokia NetAct's Scheduled Search feature under the Alarm Reports Dashboard. During scheduled task creation, user-supplied input is not validated or sanitized before storage, allowing injection of malicious JavaScript code that executes when other users view the scheduled search results.
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<= 20.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify NetAct installation and versionLocate the NetAct installation directory and check version files, typically found in /opt/nokia/netact or the installation root. Look for version.info, version.txt, or similar version metadata files.Affected if Installed version is 20.1 or earlier (any version <= 20.1)
-
Verify Scheduled Search feature is in useCheck if the Alarm Reports Dashboard module is accessible in NetAct. Navigate to the Scheduled Search function under Alarm Reports or inspect application logs for Scheduled Search-related access entries.Affected if The Scheduled Search feature has been accessed or configured in the environment
-
Inspect scheduled task configurationsAccess NetAct's database or configuration files where scheduled search tasks are stored. Look for entries in the scheduled_search or similar tables that contain the search task definitions and their parameters.Affected if Stored scheduled search tasks contain unsanitized user input in search parameters, names, or descriptions
-
Review for XSS indicators in stored dataQuery the scheduled search storage for patterns matching script tags, javascript:, or other XSS payloads in input fields such as task names, descriptions, or search criteria.Affected if Any scheduled search task records contain HTML/JavaScript code that was not filtered on input
-
Check browser execution logsReview NetAct access logs and any available security logs for XSS attempted or successful execution indicators. Also inspect browser console logs from users who accessed the Scheduled Search results.Affected if Evidence exists of JavaScript execution or attempted XSS from scheduled search result viewing
The environment is affected if Nokia NetAct version 20.1 or earlier is installed and the Scheduled Search feature under Alarm Reports Dashboard has been used, particularly if user-supplied input was stored without validation.
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 · scopedUpgrade to Nokia NetAct version 22 FP2211 or later, which includes the fix. Additionally, implement robust input validation and output encoding for all user-supplied fields in the Scheduled Search functionality.
Nokia NetAct 22 FP2211 or later
- 1. Backup the current Nokia NetAct configuration and ensure all data is properly backed up.
- 2. Plan for a maintenance window as the upgrade may require system downtime.
- 3. Download Nokia NetAct version 22 FP2211 or later from Nokia's official support portal.
- 4. Review Nokia's upgrade documentation for NetAct 20.x to 22.x to understand any prerequisites.
- 5. Execute the upgrade following Nokia's standard upgrade procedure for NetAct.
- 6. After upgrade, verify the Scheduled Search tab functionality under Alarm Reports Dashboard.
- 7. Confirm input validation is now properly enforced when creating scheduled tasks.
- 8. Validate that the XSS vulnerability is remediated by attempting to create a scheduled task with potential XSS payloads (in a test environment only).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26061 — 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-2023-26061 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