dbcve.org
Smartlink Sw HtApplication · Softing

CVE-2022-48192

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to 1.30 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site Scripting vulnerability in Softing smartLink SW-HT before 1.30, which allows an attacker to execute a dynamic script (JavaScript, VBScript) in the context of the application.

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

Cross-site scripting (XSS) vulnerability in Softing smartLink SW-HT web interface versions before 1.30 allows injection of malicious JavaScript or VBScript through unsanitized user input. The injected script executes in the context of the victim's authenticated session, potentially stealing session cookies, performing actions on behalf of the user, or redirecting to malicious sites.

MitigationUpgrade smartLink SW-HT to version 1.30 or later to obtain the vendor patch. If immediate patching is not possible, implement output encoding and input validation on the web application layer as compensating controls.

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
Smartlink Sw HtApplication
Affected:< 1.30

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the smartLink SW-HT version
    Access the web interface login page or admin panel and locate the version information, typically found in the system info, about, or settings section. If you have CLI access, check the device firmware or software version through its management interface.
    Affected if The displayed version is below 1.30 (for example, 1.20, 1.10, or earlier)
  2. Confirm the web interface is enabled
    Verify that the smartLink SW-HT web interface is actively running and accessible on the network by attempting to reach it via HTTP or HTTPS.
    Affected if The web interface is accessible and the version is below 1.30
  3. Check for existing XSS injection points
    Review web application logs or network traffic for suspicious input patterns in user-controllable fields (URL parameters, form inputs, search fields). Look for unencoded HTML characters like <script>, javascript:, or vbscript: in request parameters.
    Affected if User input fields accept and reflect special characters without encoding and the version is below 1.30

You are affected if the smartLink SW-HT web interface version is below 1.30 and the application accepts unsanitized user input through web forms or parameters.

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

Upgrade smartLink SW-HT to version 1.30 or later to obtain the vendor patch. If immediate patching is not possible, implement output encoding and input validation on the web application layer as compensating controls.

Recommended fix Moderate confidence

Smartlink SW-HT version 1.30

  1. 1. Obtain the fixed version (1.30) from Softing's official industrial website or authorized distribution channels
  2. 2. Back up current configuration and data for the smartLink SW-HT device
  3. 3. Follow Softing's standard firmware/software upgrade procedure for smartLink SW-HT
  4. 4. Verify the upgrade was successful by checking the software version
  5. 5. Confirm the XSS vulnerability is no longer present by testing for script injection in affected input fields

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

Fix this in Smartlink Sw Ht Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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