CVE-2012-0930
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 · uneditedCross-site scripting (XSS) vulnerability in Schneider Electric Modicon Quantum PLC allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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 confidenceCross-site scripting vulnerability in the web interface of Schneider Electric Modicon Quantum PLC allows remote attackers to inject malicious HTML or JavaScript code through unspecified vectors, potentially compromising operators viewing the web interface.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the device is a Modicon Quantum PLCCheck device inventory, network documentation, or use SNMP/industrial protocol discovery tools to identify the device model. Look for 'Modicon Quantum' or 'Schneider Electric Quantum' in device identification.Affected if The device is confirmed to be a Schneider Electric Modicon Quantum PLC.
-
Confirm the web interface is enabledAttempt to access the device via HTTP (port 80) or HTTPS (port 443) using the device IP address. If a login page or web interface responds, the web interface is enabled.Affected if The web interface is accessible via HTTP or HTTPS on the PLC network interface.
-
Check network exposure of the web interfacePerform a port scan on the PLC IP address focusing on ports 80 and 443. Determine if these ports are exposed to untrusted networks, VLANs, or the internet.Affected if Ports 80 or 443 are open and accessible from networks outside the trusted control system network.
-
Verify PLC is on an isolated network segmentReview network segmentation, firewall rules, and VLAN configurations to determine if the PLC is isolated from corporate IT networks and untrusted segments.Affected if The PLC web interface can be reached from networks without proper network isolation or firewall controls.
A user is affected if they operate a Modicon Quantum PLC with its web interface enabled and accessible from networks that are not fully trusted or isolated.
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 network segmentation to isolate the PLC from untrusted networks, apply input validation/sanitization on the web interface if configurable, and contact Schneider Electric for firmware updates that address this XSS vulnerability.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0930 — 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-2012-0930 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