Opcenter QualityApplication · Siemens

CVE-2023-46281

HIGH · 8.8 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 4.1 / 15 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Patch available

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
A vulnerability has been identified in Opcenter Execution Foundation (All versions < V2407), Opcenter Quality (All versions < V2312), SIMATIC PCS neo (All versions < V4.1), SINEC NMS (All versions < V2.0 SP1), Totally Integrated Automation Portal (TIA Portal) V14 (All versions), Totally Integrated Automation Portal (TIA Portal) V15.1 (All versions), Totally Integrated Automation Portal (TIA Portal) V16 (All versions), Totally Integrated Automation Portal (TIA Portal) V17 (All versions < V17 Update 8), Totally Integrated Automation Portal (TIA Portal) V18 (All versions < V18 Update 3). When accessing the UMC Web-UI from affected products, UMC uses an overly permissive CORS policy. This could allow an attacker to trick a legitimate user to trigger unwanted behavior.

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

A detailed technical summary for this CVE is being prepared.

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
Opcenter QualityApplication
Affected:all versions
Simatic Pcs NeoApplication
Affected:< 4.1
Sinumerik Integrate Runmyhmi \/automotiveApplication
Affected:all versions
Totally Integrated Automation PortalApplication
Affected:>= 14.0, < 15>= 15, < 16>= 16, < 17>= 17, < 18all versions= 18

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
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

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 4.1 / 15 / 16 or later
Fixed in 4.11516
Recommended fix High confidence

Product-specific: Opcenter Execution Foundation V2407, Opcenter Quality V2312, SIMATIC PCS neo V4.1, SINEC NMS V2.0 SP1, TIA Portal V17 Update 8, or TIA Portal V18 Update 3

  1. 1. Identify the specific Siemens product from the affected list: Opcenter Execution Foundation, Opcenter Quality, SIMATIC PCS neo, SINEC NMS, or Totally Integrated Automation Portal (TIA Portal)
  2. 2. Determine the current installed version of the affected product
  3. 3. For Opcenter Execution Foundation: upgrade to version V2407 or later
  4. 4. For Opcenter Quality: upgrade to version V2312 or later
  5. 5. For SIMATIC PCS neo: upgrade to version V4.1 or later
  6. 6. For SINEC NMS: upgrade to version V2.0 SP1 or later
  7. 7. For TIA Portal V14, V15.1, or V16: upgrade to a newer major version (V17 or V18)
  8. 8. For TIA Portal V17: upgrade to V17 Update 8 or later
Caveat Major version upgrades (e.g., TIA Portal V14/V15/V16 to V17/V18) may introduce compatibility changes with existing projects and require thorough testing

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46281 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