CVE-2023-2072
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 · uneditedThe Rockwell Automation PowerMonitor 1000 contains stored cross-site scripting vulnerabilities within the web page of the product. The vulnerable pages do not require privileges to access and can be injected with code by an attacker which could be used to leverage an attack on an authenticated user resulting in remote code execution and potentially the complete loss of confidentiality, integrity, and availability of the product.
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 confidenceStored cross-site scripting vulnerability in Rockwell Automation PowerMonitor 1000 web interface. An unauthenticated attacker can inject malicious JavaScript into web pages that persist on the server. When authenticated users view these compromised pages, the script executes in their browser context, potentially allowing session hijacking, privilege escalation, and ultimately remote code execution on the device.
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 dataall versionsCVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the web interface or check the device nameplate/documentation to confirm the model is Rockwell Automation PowerMonitor 1000. The web interface typically shows device information on the login page or status page.Affected if The device is a PowerMonitor 1000 with web interface enabled
-
Verify web interface is enabledAttempt to access the PowerMonitor 1000 web interface by entering the device IP address in a web browser. If a login page or status page loads, the web interface is enabled.Affected if The web interface is accessible and responds to HTTP requests
-
Check for unexpected or suspicious content in web pagesView the source of web pages (right-click > View Page Source) or inspect elements using browser developer tools. Look for any unexpected script tags, event handlers, or encoded content that may indicate injected XSS payloads.Affected if Any user-supplied data displayed on web pages contains unencoded or unsanitized JavaScript syntax such as <script>, javascript:, or event handlers like onload/onerror
-
Review web server access logs for injection attemptsIf accessible, examine the device or upstream web server logs for patterns like <script>, javascript:, or other XSS vectors in request parameters. Check for repeated or unusual entries from external IP addresses.Affected if Logs contain XSS injection patterns in parameters that store and display user data
A user is affected if they have a PowerMonitor 1000 with the web interface enabled, as all firmware versions are vulnerable to stored XSS attacks.
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 dataImplement output encoding and input validation/sanitization on all web page inputs that store and display user-supplied data. Apply Content Security Policy headers to mitigate XSS execution. For industrial control devices, coordinate patch deployment through proper change management procedures.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2072 — 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-2023-2072 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