Skip to content
Fencer Intel
high 8.0

CVE-2013-3633 json

A vulnerability has been identified in SCALANCE X-200 switch family (incl.

published 2013-05-24 13 y ago modified 2026-06-16 4 mo ago also EUVD-2013-3566

cvss
8.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

A vulnerability has been identified in SCALANCE X-200 switch family (incl. SIPLUS NET variants) (Versions < V5.0.0 for CVE-2013-3633 and versions < V4.5.0 for CVE-2013-3634), SCALANCE X-200IRT switch family (incl. SIPLUS NET variants) (All versions < V5.1.0). The user privileges for the web interface are only enforced on client side and not properly verified on server side. Therefore, an attacker is able to execute privileged commands using an unprivileged account.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-13-169-01 updated cvss 8.0

Siemens Scalance X200 IRT Multiple Vulnerabilities

  • Siemens SCALANCE X200-4P IRT <V5.1.0 Siemens SCALANCE X201-3P IRT <V5.1.0 Siemens SCALANCE X201-3P IRT PRO <V5.1.0 Siemens SCALANCE X202-2IRT <V5.1.0 Siemens SCALANCE X202-2P IRT <V5.1.0 Siemens SCALANCE X202-2P IRT PRO <V5.1.0
    +3 more products
    Siemens SCALANCE X204IRT <V5.1.0 Siemens SCALANCE X204IRT PRO <V5.1.0 Siemens SCALANCE XF204IRT <V5.1.0
    affected: mitigation “Siemens update information is located here: (http://support.automation.siemens.com/WW/view/en/73470284)” cert-portal.siemens.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 8.0 AV:N/AC:L/Au:S/C:P/I:P/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.