Skip to main content
No exploitation reportedFix available

CVE-2022-33137

No exploitation reported by the sources we read.

  • Published2022-07-12
  • Fixed in3.3
  • WeaknessCWE-613

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A vulnerability has been identified in SIMATIC MV540 H (All versions < V3.3), SIMATIC MV540 S (All versions < V3.3), SIMATIC MV550 H (All versions < V3.3), SIMATIC MV550 S (All versions < V3.3), SIMATIC MV560 U (All versions < V3.3), SIMATIC MV560 X (All versions < V3.3). The web session management of affected devices does not invalidate session ids in certain logout scenarios. This could allow an authenticated remote attacker to hijack other users' sessions.

Timeline

dates in UTC
  1. 2022-07-1210:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-33137?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-33137?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Siemens simatic mv540 h firmwareversion to verify
BranchAffectedFixed in
3.3< 3.33.3
Siemens simatic mv540 s firmwareversion to verify
BranchAffectedFixed in
3.3< 3.33.3
Siemens simatic mv550 h firmwareversion to verify
BranchAffectedFixed in
3.3< 3.33.3

3 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-22-195-03 CISA6 known affected

    Siemens SIMATIC MV500 Devices

    SIMATIC MV540 H · SIMATIC MV540 S · SIMATIC MV550 H · +3 more

Full record on NVD

Fix

  1. Update Siemens simatic mv540 h firmware to 3.3
  2. Vendor fix CISA ICSA-22-195-03 · 6 productsUpdate to V3.3 or later version

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.18read 2026-10-23
  • NVDCVSS 2.06read 2026-10-23
  • CNAweakness (CWE)CWE-613read 2026-10-23
  • NVDweakness (CWE)CWE-613read 2026-10-23
  • FIRST EPSSEPSS score0.9 %2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Published
2022-07-12
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-33137?

A vulnerability has been identified in SIMATIC MV540 H (All versions < V3.3), SIMATIC MV540 S (All versions < V3.3), SIMATIC MV550 H (All versions < V3.3), SIMATIC MV550 S (All versions < V3.3), SIMATIC MV560 U (All versions < V3.3), SIMATIC MV560 X (All versions < V3.3). The web session management of affected devices does not invalidate session ids in certain logout scenarios. This could allow an authenticated remote attacker to hijack other users' sessions.

Is CVE-2022-33137 actively exploited?

Active exploitation of CVE-2022-33137 has not been confirmed. Its EPSS score was 0.9% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-33137?

CVE-2022-33137 has a CVSS v3 base score of 8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H.

Running SIMATIC MV540 H (All versions <? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month