LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30280: /SecurityManagement/html/createuser.jsf in Nokia NetAct 22 allows CSRF.

/SecurityManagement/html/createuser.jsf in Nokia NetAct 22 allows CSRF. A remote attacker is able to create users with arbitrary privileges, even administrative privileges. The application (even if it implements a CSRF token for the random GET request) does not ever verify a CSRF token. With a little help of social engineering/phishing (such as sending a link via email or chat), an attacker may trick the users of a web application into executing actions of the attacker's choosing. If the victim is a normal user, a successful CSRF attack can force the user to perform state changing requests like transferring funds, changing their email address, and so forth. If the victim is an administrative account, CSRF can compromise the entire web application.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue lets an attacker abuse a logged-in Nokia NetAct 22 user’s browser to create new accounts, potentially with administrator privileges. The source bundle does not provide CVSS, patch, or affected-version detail beyond the NetAct 22 description, but the business impact could be full compromise of the management application.

Executive priority

Treat this as a high-priority exposure check for any Nokia NetAct 22 environment. The urgency comes from potential administrator account creation, but response should be evidence-led because the public record lacks CVSS, patch, and active-exploitation confirmation.

Technical view

CVE-2022-30280 describes missing CSRF token verification in /SecurityManagement/html/createuser.jsf in Nokia NetAct 22. A remote attacker could use social engineering to cause an authenticated user to submit state-changing account-creation requests with arbitrary privileges. The structured affected fields are marked n/a, so exposure metadata is incomplete.

Likely exposure

Likely exposure is limited to organizations running Nokia NetAct 22 SecurityManagement. Risk is highest where the interface is reachable from administrator workstations and privileged users maintain active sessions while using email, chat, or web links. The bundle does not confirm broader product or version impact.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The described attack depends on tricking an authenticated user; if that user is an administrator, the result may be complete compromise of the web application.

Researcher notes

Key gaps are the absence of CVSS, CWE mapping, structured affected versions, and vendor remediation details in the provided bundle. The description is specific about endpoint and impact, but validation should avoid assuming impact outside Nokia NetAct 22 without vendor confirmation.

Mitigation direction

  • Check Nokia or operator guidance for patched NetAct 22 releases or official mitigations.
  • Restrict SecurityManagement access to trusted admin networks and managed workstations.
  • Reduce admin session lifetime and require reauthentication for user-management actions.
  • Review existing accounts and remove unauthorized or excessive privileges.
  • Monitor user-creation events and privilege changes for suspicious activity.

Validation and detection

  • Inventory whether Nokia NetAct 22 SecurityManagement is deployed.
  • Confirm whether /SecurityManagement/html/createuser.jsf is reachable from user workstations.
  • Review application logs for unexpected account creation or privilege grants.
  • Use approved testing to verify CSRF token enforcement on user-management actions.
  • Confirm administrative access is segmented and limited to trusted operators.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-30280 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.