CVE-2020-7004 json
VISAM VBASE Editor version 11.5.0.2 and VBASE Web-Remote Module may allow weak or insecure permissions on the VBASE directory resulting in…
published 6y ago modified 4mo ago also EUVD-2020-28144
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
VISAM VBASE Editor version 11.5.0.2 and VBASE Web-Remote Module may allow weak or insecure permissions on the VBASE directory resulting in elevation of privileges or malicious effects on the system the next time a privileged user runs the application.
Is CVE-2020-7004 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-20-084-01 updated cvss 8.2
VISAM Automation Base (VBASE) (Update B)
-
VISAM VBASE Editor 11.5.0.2affected: mitigation “VISAM recommends users update to VBASE v11.7.0.2 or later. A download link will be provided 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
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- VISAM VBASE Editor
- VISAM VBASE Web-Remote Module
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
us-cert.gov
/ics/advisories/icsa-20-084-01
mitigation, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2020-7004
- NVD CVE-2020-7004
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.