dbcve.org
Powersystem CenterApplication · Subnet

CVE-2023-32659

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-19
Fix available
A fix is available. Upgrade to 2020 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
SUBNET PowerSYSTEM Center versions 2020 U10 and prior contain a cross-site scripting vulnerability that may allow an attacker to inject malicious code into report header graphic files that could propagate out of the system and reach users who are subscribed to email notifications.

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

Stored cross-site scripting vulnerability in SUBNET PowerSYSTEM Center allows attackers to inject malicious JavaScript code into report header graphic files. When users receive email notifications containing these reports, the injected code executes in their browsers, enabling session hijacking, credential theft, or further propagation.

MitigationImplement strict input validation and sanitization on graphic file uploads, and apply output encoding when rendering report content in email notifications to prevent script execution.

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
Powersystem CenterApplication
Affected:< 2020= 2020

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 installed Subnet PowerSYSTEM Center version
    Locate the application version through the software's built-in About dialog, help menu, or installation directory version file. Compare the version number against the affected ranges (2020 and below).
    Affected if The installed version is 2020 or any version prior to 2020.
  2. Verify email notification feature is active
    Access the application administration console or configuration settings and locate the email notification module. Confirm whether users can receive automated email reports.
    Affected if Email notifications are enabled and configured to deliver reports to users.
  3. Confirm report generation with graphics is permitted
    Review the report configuration settings to determine if the application allows embedding or attaching graphic files (such as headers, logos, or images) within generated reports.
    Affected if The report generation feature includes support for graphic file inclusion in report output.
  4. Inspect email rendering configuration
    Check the email notification settings for how report content (including graphics) is rendered when messages are composed and sent to users.
    Affected if Email notifications render HTML content from report graphics without sanitization.

A user is affected if running Subnet PowerSYSTEM Center version 2020 or earlier with email notifications enabled for reports that include graphic files, allowing unsanitized graphic content to execute in email recipients' browsers.

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

Implement strict input validation and sanitization on graphic file uploads, and apply output encoding when rendering report content in email notifications to prevent script execution.

Recommended fix Moderate confidence

Any version of SUBNET PowerSYSTEM Center released after 2020 U10 that includes the security fix

  1. 1. Identify the current installed version of SUBNET PowerSYSTEM Center by accessing the system administration or about section
  2. 2. Determine if the installed version is 2020 U10 or prior
  3. 3. Contact SUBNET technical support or visit the official SUBNET website to obtain the latest version that addresses CVE-2023-32659
  4. 4. Download the updated version from a trusted source provided by SUBNET
  5. 5. Before upgrading, backup the current system configuration and any critical data
  6. 6. Follow SUBNET's documented upgrade procedure to apply the update
  7. 7. After upgrading, verify that the vulnerability is remediated by checking that report header graphic files are properly sanitized
Caveat Review release notes for any configuration or compatibility changes between 2020 U10 and the target upgrade version

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

Fix this in Powersystem Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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