CVE-2021-42537 json
VISAM VBASE Editor Improper Restriction of XML
published 2022-07-27 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-29506
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
VISAM VBASE version 11.6.0.6 processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-21-308-01 updated cvss 5.9
VISAM VBASE Editor
-
VISAM VBASE Pro-RT/ Server-RT (Web Remote) 11.6.0.6affected: mitigation “VISAM recommends users update to VBASE v11.7.0.2 or later. Users may obtain a download link by submitting a request form.” vbase.net
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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- VISAM VBASE Pro-RT/ Server-RT (Web Remote)
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
cisa.gov
/uscert/ics/advisories/icsa-21-308-01
mitigation, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2021-42537
- NVD CVE-2021-42537
Fencer Vulns 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.