Skip to main content
VulnerabilityPublished Updated

CVE-2022-32555: Unisys Data Exchange Management Studio · Cross-Site Request Forgery (CSRF)

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 16:39 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediate verification of the Unisys Data Exchange Management Studio version in use is essential. Organizations should upgrade to versions 6.0.IC2 or later in the 6.x series, or 7.0.IC1 or later in the 7.x series, where the Anti-CSRF protections are presumably implemented.
  2. If patching is not immediately possible, implement compensating controls such as restricting access to the management studio interface to trusted internal networks or VPNs to reduce exposure.
  3. Employ web application firewalls (WAFs) with rules designed to detect and block CSRF attack patterns and suspicious POST requests lacking valid tokens.
  4. Educate users about the risks of phishing and social engineering to minimize the chance of user interaction that triggers CSRF attacks.
  5. Monitor logs for unusual POST requests or unexpected changes in data exchange configurations that could indicate exploitation attempts.
  6. Coordinate with Unisys support or security advisories to obtain official patches or guidance.
  7. Review and enforce strict session management and implement additional authentication factors where possible to limit the impact of forged requests. These measures, combined with prompt patching, will significantly reduce the risk posed by this vulnerability.

Description

Unisys Data Exchange Management Studio before 6.0.IC2 and 7.x before 7.0.IC1 doesn't have an Anti-CSRF token to authenticate the POST request. Thus, a cross-site request forgery attack could occur.

References

Community reviews

Loading reviews…