CVE-2019-10933
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 · uneditedA vulnerability has been identified in Spectrum Power 3 (Corporate User Interface) (All versions <= v3.11), Spectrum Power 4 (Corporate User Interface) (Version v4.75), Spectrum Power 5 (Corporate User Interface) (All versions < v5.50), Spectrum Power 7 (Corporate User Interface) (All versions <= v2.20). The web server could allow Cross-Site Scripting (XSS) attacks if unsuspecting users are tricked into accessing a malicious link. User interaction is required for a successful exploitation. The user does not need to be logged into the web interface in order for the exploitation to succeed.At the stage of publishing this security advisory no public exploitation is known.
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 confidenceCross-Site Scripting (XSS) vulnerability in the Corporate User Interface of Siemens Spectrum Power 3/4/5/7. An unauthenticated attacker can inject malicious JavaScript code via the web interface that executes in victim browsers when users access a crafted malicious link. User interaction is required but no authentication is needed.
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<= 3.11<= 4.75<= 5.50<= 2.20CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Siemens Spectrum Power installationCheck the system for Siemens Spectrum Power installation directories (typically under C:\Program Files\Siemens\Spectrum Power or /opt/siemens/spectrum) and look for version information in registry, installation logs, or product information filesAffected if Spectrum Power 3, 4, 5, or 7 is installed and version is at or below 3.11, 4.75, 5.50, or 2.20 respectively
-
Determine the exact Spectrum Power versionRun 'Spectrum Power version' command if available, or check the product's about/info screen accessible from the application menu, or examine version files in the installation directoryAffected if Installed version number is equal to or lower than the affected ranges for the respective product line
-
Verify the Corporate User Interface component is presentCheck for the web interface service/process (typically named 'Spectrum Power Web' or similar) running on the system, and look for web application files in the installation directory under a 'web' or 'ui' folderAffected if The Corporate User Interface web component is installed and running
-
Confirm web interface accessibilityAttempt to access the web interface URL (default ports 80/443 or configured ports) from a browser or curl command to verify it responds without authenticationAffected if The Corporate User Interface is accessible over the network without requiring login credentials (unauthenticated access is possible)
-
Check network exposure of the web interfaceReview firewall rules, network configuration, and IIS/Apache settings to determine if the web interface is exposed to internal or external networksAffected if The web interface is reachable from network segments beyond the local host, increasing exposure to unauthenticated attackers
You are affected if Siemens Spectrum Power 3 (<=3.11), 4 (<=4.75), 5 (<=5.50), or 7 (<=2.20) is installed with the Corporate User Interface enabled and accessible, because the XSS flaw can be exploited by unauthenticated attackers via malicious links.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches when available; implement input validation and output encoding in the web interface; consider WAF rules as compensating control until patches are applied.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10933 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10933 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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