How severe is CVE-2020-21122?

CVE-2020-21122 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-21122?

CVE-2020-21122 affects the following packages: com.bstek.ureport:ureport2-console (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-21122?

No patched version of com.bstek.ureport:ureport2-console has shipped for CVE-2020-21122 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2020-21122 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.bstek.ureport:ureport2-console, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-21122 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2020-21122 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2020-21122, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-21122?

CVE-2020-21122 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-21122?

CVE-2020-21122 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2020-21122 published, and has it been updated?

CVE-2020-21122 was published on September 15, 2021 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2020-21122 — ureport2-console

MEDIUM

CVE-2020-21122 is a medium-severity (CVSS 5.3) Server-Side Request Forgery (SSRF) vulnerability in com.bstek.ureport:ureport2-console. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Server-Side Request Forgery in UReport

Also known asGHSA-6q3p-36f4-cwxv

Published

Sep 15, 2021

Updated

Aug 7, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-21122 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕com.bstek.ureport:ureport2-console

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

UReport v2.2.9 contains a Server-Side Request Forgery (SSRF) in the designer page which allows attackers to detect intranet device ports.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.bstek.ureport:ureport2-console`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

ureportureport_project

1 version

2.2.9

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

UReport v2.2.9 contains a Server-Side Request Forgery (SSRF) in the desi…

github.comNVDSep 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.bstek.ureport:ureport2-console, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of com.bstek.ureport:ureport2-console has shipped for CVE-2020-21122 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

UReport v2.2.9 contains a Server-Side Request Forgery (SSRF) in the designer page which allows attackers to detect intranet device ports.

O3 Security · Impact-Aware SCA

Is CVE-2020-21122 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

ureport

1.7/10

Code-Review0/10

Maintained0/10

Branch-Protection0/10

Assessed Oct 5, 2026

Timeline

Disclosed

Sep 15, 2021

First exploit

Sep 28, 2021

Last updated

Aug 7, 2026

Identifiers

CVE-2020-21122

GHSA-6q3p-36f4-cwxv

References

Advisorynvd.nist.gov Reportgithub.com Packagegithub.com

Related vulnerabilities

Also affects ureport2-console

This CVE is medium severity; 1 of 1 other CVE affecting ureport2-console is rated as high or higher (top: critical).

CVE-2022-25767

Same weakness: CWE-918

This CVE is medium severity; 7 of 7 other CVEs with CWE-918 are rated as high or higher (top: critical).

GHSA-39wr-7q6h-cf68GHSA-jgh3-fggc-mcpmCVE-2026-85732CVE-2026-59823CVE-2026-61793CVE-2026-73247CVE-2026-61559Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 7, 2026

CVE-2020-21122 — ureport2-console

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2020-21122 in your dependencies?