dbcve.org
Smartpower WebApplication · Gruparge

CVE-2022-45087

MEDIUM · 6.1 CVSS v3.1 Published 2023-02-12
Fix available
A fix is available. Upgrade to 23.01.01 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Group Arge Energy and Control Systems Smartpower Web allows Cross-Site Scripting (XSS). This issue affects Smartpower Web: before 23.01.01.

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 Group Arge Energy and Control Systems Smartpower Web allows attackers to inject malicious scripts through unsanitized user input that gets rendered in web pages. This occurs due to improper neutralization of input during web page generation, potentially enabling session hijacking, credential theft, or defacement. The vulnerability affects versions before 23.01.01.

MitigationUpdate Smartpower Web to version 23.01.01 or later which contains the security fix. If immediate patching is not feasible, implement proper input validation and output encoding at all user input points in the web application.

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
Smartpower WebApplication
Affected:< 23.01.01

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 installed Smartpower Web version
    Check the application version through the web interface (typically found in About, Settings, or footer), or check the version information in the installation directory if you have direct server access. Compare the found version against the affected range of versions before 23.01.01.
    Affected if The installed version is any release prior to 23.01.01
  2. Determine if the web interface is accessible
    Access the Smartpower Web URL through a browser or curl command. Confirm the application is running and responding to HTTP/HTTPS requests.
    Affected if The web interface is accessible and running a vulnerable version
  3. Identify user input fields in the application
    Navigate through the Smartpower Web interface and locate all input fields, forms, or parameters that accept user data (login fields, search boxes, configuration inputs, or any parameter in the URL).
    Affected if The application has user input fields and is running a version before 23.01.01
  4. Inspect web page source for unsanitized output
    Use browser developer tools or curl to retrieve web pages, then view the source code around user-supplied input. Check if special characters like <, >, ", ' are being rendered as plain text or HTML-encoded.
    Affected if User input is reflected in pages without proper encoding and the version is below 23.01.01

A user is affected if Smartpower Web version 23.01.01 or later is not installed and the application exposes user input fields that render without sanitization.

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

Update Smartpower Web to version 23.01.01 or later which contains the security fix. If immediate patching is not feasible, implement proper input validation and output encoding at all user input points in the web application.

Recommended fix Moderate confidence

Smartpower Web version 23.01.01 or later

  1. 1. Identify the current version of Smartpower Web installation by accessing the admin interface or system information page.
  2. 2. If version is below 23.01.01, plan for upgrade during a maintenance window.
  3. 3. Backup all configuration files, user data, and system settings according to vendor backup procedures.
  4. 4. Obtain the Smartpower Web version 23.01.01 or later upgrade package from Group Arge Energy and Control Systems official sources.
  5. 5. Apply the upgrade following the vendor's documented upgrade procedure for Smartpower Web.
  6. 6. After upgrade, verify the application is functioning correctly and the XSS vulnerability is resolved.
  7. 7. Confirm the installed version is 23.01.01 or later.
Caveat Review vendor release notes for version 23.01.01 to check for any configuration or functionality changes that may require adjustment

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

Fix this in Smartpower Web Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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