CVE-2020-27998 is a critical-severity (CVSS 9.8) CWE-862 vulnerability in FastReport.OpenSource. 1 public exploit reference exists, so weaponization risk is real. A fix is available for FastReport.OpenSource — see the affected versions and patch details below.
Missing Authorization in FastReport
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-27998 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
FastReport.OpenSourceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in FastReport before 2020.4.0. It lacks a ScriptSecurity feature and therefore may mishandle (for example) GetType, typeof, TypeOf, DllImport, LoadLibrary, and GetProcAddress.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | FastReport.OpenSource | all versions | 2020.4.0dotnet add package FastReport.OpenSource --version 2020.4.0 |
Affected Products
fastreportfast-reportResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for FastReport.OpenSource, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update FastReport.OpenSource to 2020.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-27998 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2020-27998 in your dependencies?
Find it across NuGet, including transitive dependencies.