CVE-2020-7932 json
OMERO-web Sensitive Data Exposure
published 6y ago modified 4mo ago also GHSA-vwxv-frj6-fhc9 , PYSEC-2020-244 , EUVD-2020-0120
- cvss
- 5.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
OMERO.web before 5.6.3 optionally allows sensitive data elements (e.g., a session key) to be passed as URL query parameters. If an attacker tricks a user into clicking a malicious link in OMERO.web, the information in the query parameters may be exposed in the Referer header seen by the target. Information in the URL path such as object IDs may also be exposed.
Patch / fix
- pypi omero-web 5.6.3
- openmicroscopy omero.web 5.6.3
Is CVE-2020-7932 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | omero-web | <5.6.3 |
5.6.3 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
openmicroscopy.org
/security/advisories/2019-SV4/
vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-7932
advisory
-
github.com
/ome/omero-web
package
-
github.com
/pypa/advisory-database/tree/main/vulns/omero-web/PYSEC-2020-244.yaml
web
-
openmicroscopy.org
/security/advisories/2019-SV4
web
-
github.com
/advisories/GHSA-vwxv-frj6-fhc9
advisory
Sources
- CVE List CVE-2020-7932
- GitHub Advisory GHSA-vwxv-frj6-fhc9
- NVD CVE-2020-7932
- OSV PYSEC-2020-244
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.