dbcve.org
Smartpower WebApplication · Gruparge

CVE-2022-45088

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-12
Fix available
A fix is available. Upgrade to 23.01.01 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Input Validation vulnerability in Group Arge Energy and Control Systems Smartpower Web allows PHP Local File Inclusion. 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 · moderate confidence

Improper input validation in Smartpower Web allows attackers to manipulate PHP file inclusion mechanisms to read sensitive files from the server filesystem. This Local File Inclusion (LFI) vulnerability enables unauthorized access to configuration files, source code, and system files such as /etc/passwd.

MitigationUpgrade Smartpower Web to version 23.01.01 or later which contains proper input validation to prevent path traversal in file inclusion operations.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Smartpower Web version
    Locate the application and determine its version number through the web interface, configuration files, or application metadata
    Affected if The version is below 23.01.01 (for example, 23.01.00 or earlier)
  2. Confirm the web application is accessible
    Verify that the Smartpower Web interface is running and reachable on the network
    Affected if The web interface is exposed and operational
  3. Check for PHP file inclusion functionality
    Inspect the web application for PHP scripts that accept user input to include or require files
    Affected if The application contains file inclusion mechanisms that process user-supplied input without proper validation
  4. Verify the file inclusion endpoint accepts path parameters
    Test or inspect PHP endpoints that handle file path arguments to determine if path traversal sequences are filtered
    Affected if The file inclusion parameters do not sanitize or reject path traversal sequences like ../

The environment is affected if Gruparge Smartpower Web version is below 23.01.01 and the web application exposes PHP file inclusion functionality that accepts unsanitized path input.

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

Upgrade Smartpower Web to version 23.01.01 or later which contains proper input validation to prevent path traversal in file inclusion operations.

Recommended fix High confidence

23.01.01

  1. Create a full backup of the current Smartpower Web installation including all configuration files and data
  2. Download the fixed version 23.01.01 from the official Group Arge Energy and Control Systems vendor
  3. Review the vendor's upgrade documentation for any specific migration procedures
  4. Stop the Smartpower Web service before performing the upgrade
  5. Install version 23.01.01 following the vendor's standard upgrade procedure
  6. After installation, verify that all web application files have been properly updated
  7. Start the Smartpower Web service and confirm normal operation
  8. If available, review access logs to ensure no exploitation occurred prior to the upgrade

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

Fix this in Smartpower Web Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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