Code InjectionWeakness · CWE-94

CVE-2022-31491

CRITICAL · 10.0 CVSS v3.1 Published 2025-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Voltronic Power ViewPower through 1.04-24215, ViewPower Pro through 2.0-22165, and PowerShield Netguard before 1.04-23292 allows a remote attacker to run arbitrary code via an unspecified web interface related to detection of a managed UPS shutting down. An unauthenticated attacker can use this to run arbitrary code immediately regardless of any managed UPS state or presence.

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

Critical unauthenticated remote code execution vulnerability in the web interface of ViewPower and PowerShield Netguard UPS management software. An attacker can execute arbitrary code without authentication by exploiting the web interface related to UPS shutdown detection functionality.

MitigationApply vendor patches (ViewPower 1.04-24216+, ViewPower Pro 2.0-22166+, PowerShield Netguard 1.04-23292+), restrict network access to the management web interface, and consider network segmentation for UPS management systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 if ViewPower or PowerShield Netguard web interface is running
    Access the management web interface on the server (typically ports 80, 443, or 8080). Look for login pages or system status pages identifying the software product.
    Affected if The web interface is accessible and responds with ViewPower or PowerShield Netguard branding
  2. Determine the installed software version
    Check the web interface for version information, typically found in About, System Info, or Help pages. Alternatively, check installed software listings on the host system.
    Affected if Version cannot be determined or shows a version prior to 1.04-24216 for ViewPower, prior to 2.0-22166 for ViewPower Pro, or prior to 1.04-23292 for PowerShield Netguard
  3. Check if the UPS shutdown detection feature is enabled
    Inspect the web interface configuration settings for UPS shutdown or power failure detection features. This is typically found in Power/Energy Settings, UPS Configuration, or Shutdown Settings sections.
    Affected if The UPS shutdown detection feature is configured and active in the web interface
  4. Verify network exposure of the management interface
    Review firewall rules or network configuration to determine if the web interface is exposed to untrusted networks or the internet.
    Affected if The web interface is accessible from untrusted network segments or directly from the internet

A user is affected if ViewPower (version < 1.04-24216), ViewPower Pro (version < 2.0-22166), or PowerShield Netguard (version < 1.04-23292) is running with its web interface accessible and the UPS shutdown detection feature is enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches (ViewPower 1.04-24216+, ViewPower Pro 2.0-22166+, PowerShield Netguard 1.04-23292+), restrict network access to the management web interface, and consider network segmentation for UPS management systems.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31491 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