CVE-2022-48199
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 · uneditedSoftPerfect NetWorx 7.1.1 on Windows allows an attacker to execute a malicious binary with potentially higher privileges via a low-privileged user account that abuses the Notifications function. The Notifications function allows for arbitrary binary execution and can be modified by any user. The resulting binary execution will occur in the context of any user running NetWorx. If an attacker modifies the Notifications function to execute a malicious binary, the binary will be executed by every user running NetWorx on that system.
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 confidenceSoftPerfect NetWorx 7.1.1 contains a local privilege escalation vulnerability in its Notifications function. Any local user can modify the notification configuration to point to an arbitrary binary, which will execute in the security context of any other user who subsequently runs NetWorx on the same system, enabling lateral movement across user accounts.
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= 7.1.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SoftPerfect NetWorx is installedCheck for NetWorx installation by looking in Program Files or Program Files (x86) for a NetWorx folder, or check the Windows uninstall list (reg query 'HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall' /s for DisplayName containing NetWorx)Affected if NetWorx version 7.1.1 is found installed on the system
-
Check installed NetWorx version numberIf NetWorx is installed, locate the main executable (usually networx.exe) in the installation directory and check its version properties, or use wmic product where 'Name like "%NetWorx%"' get VersionAffected if The installed version is exactly 7.1.1
-
Locate NetWorx notification configuration fileSearch for configuration files in the NetWorx installation directory and in user AppData folders (e.g., %APPDATA%\SoftPerfect\NetWorx or %LOCALAPPDATA%\SoftPerfect\NetWorx) for files with names containing 'notification' or 'config'Affected if A NetWorx notification configuration file exists on the system
-
Verify configuration file permissionsRight-click the identified notification configuration file, go to Properties > Security, and check which users or groups have Write or Modify permissions. Alternatively, use icacls <filename> to list effective permissionsAffected if Non-admin users or the Users group have Write or Modify permissions on the notification configuration file
-
Examine notification configuration for suspicious binary pathsOpen the notification configuration file (if it is text-based like XML, JSON, or INI) in a text editor and look for entries under notification settings that point to executable paths. Check if any path references a binary outside the NetWorx installation directoryAffected if The notification configuration contains a path pointing to an arbitrary executable not in the standard NetWorx installation folder
A user is affected if NetWorx version 7.1.1 is installed AND non-privileged users have write access to the notification configuration file, allowing them to modify it to point to arbitrary binaries for execution by other users.
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 · scopedApply file system permissions to restrict modification of NetWorx configuration files to administrators only, and update to a patched version when available. Audit the NetWorx installation directory for unauthorized binary modifications.
NetWorx 7.1.2 or later
- 1. Navigate to the official SoftPerfect website at www.softperfect.com
- 2. Download the latest version of NetWorx (version 7.1.2 or later)
- 3. Uninstall the current vulnerable version (7.1.1) from the system
- 4. Install the newly downloaded version
- 5. Verify that the Notifications function now has proper permission controls that prevent modification by non-privileged users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48199 — 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-2022-48199 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