CVE-2024-36140
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 OZW672 (All versions < V5.2), OZW772 (All versions < V5.2). The user accounts tab of affected devices is vulnerable to stored cross-site scripting (XSS) attacks. This could allow an authenticated remote attacker to inject arbitrary JavaScript code that is later executed by another authenticated victim user with potential higher privileges than the attacker.
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 confidenceStored cross-site scripting (XSS) vulnerability in the user accounts tab of OZW672 and OZW772 devices (all versions < V5.2). An authenticated attacker can inject malicious JavaScript code that persists on the device and executes when other authenticated users with higher privileges access the affected page.
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< 5.2< 5.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the device modelAccess the device web interface or administrative console and locate the device information or status page to confirm the exact model (OZW672 or OZW772).Affected if The device is not an OZW672 or OZW772 model.
-
Determine the installed firmware versionLocate the firmware version information in the device's system settings, status page, or about section. Compare the version number to 5.2.Affected if The firmware version is below V5.2 (for example, V5.0, V4.x, etc.).
-
Verify user accounts functionality is enabledNavigate to the user accounts tab or user management section of the device web interface. Confirm that the user management feature is accessible and functional.Affected if The user accounts tab is present and accessible on the device.
-
Confirm authenticated access to the deviceLog into the device with any valid user account credentials to verify the authentication mechanism is operational.Affected if Authentication succeeds and grants access to the device interface.
The device is affected if it is an OZW672 or OZW772 model running firmware version below V5.2 and the user accounts tab is accessible after authentication.
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.
dbcve · scoped5.2
Upgrade OZW672 and OZW772 devices to firmware version V5.2 or later to resolve the stored XSS vulnerability in the user accounts tab.
Firmware V5.2 for OZW672 and OZW772
- Obtain the V5.2 firmware update for OZW672 or OZW772 from the official Siemens support portal (cert-portal.siemens.com or siemens.com/support)
- Access the web interface of the affected device using administrator credentials
- Navigate to the firmware update or system maintenance section of the web interface
- Upload the V5.2 firmware file and initiate the upgrade process
- Wait for the firmware update to complete and the device to reboot
- Log in to the device and verify the firmware version shows V5.2
- Clear browser cache and test that the user accounts tab functions correctly without XSS vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36140 — 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-2024-36140 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