CVE-2020-25540

HIGHNVD 7.58.8
EchelonGraph scoreHIGH confidence

Score elevated to 8.8 because EPSS predicts 76% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 76%
CISA-KEV: Not listedEPSS: 76%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ThinkAdmin v6 is affected by a directory traversal vulnerability. An unauthorized attacker can read arbitrarily file on a remote server via GET request encode parameter.

CVSS v3
7.5
EG Score
8.8(high)
EG Risk
74(Track)
EG Risk 74/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation76% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.5%
KEV
Not listed

Published

September 14, 2020

Last Modified

November 21, 2024

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
composerzoujingli/thinkadminghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
zoujingli/thinkadmin6.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:51 UTCEG score recompute 1.30
  2. 2026-07-22 22:37 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-15 16:55 UTCEPSS rescore
  7. 2026-07-13 06:10 UTCEPSS rescore
  8. 2026-07-13 06:10 UTCEPSS rescore
  9. 2026-07-11 08:25 UTCEPSS rescore
  10. 2026-07-11 08:25 UTCEPSS rescore
  11. 2026-07-09 19:07 UTCEPSS rescore
  12. 2026-07-06 16:25 UTCEPSS rescore
  13. 2026-07-06 16:25 UTCEPSS rescore
  14. 2026-07-01 15:03 UTCEPSS rescore
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-16 17:50 UTCEPSS rescore
Show 16 more
  1. 2026-06-16 17:50 UTCEPSS rescore
  2. 2026-06-15 17:46 UTCEPSS rescore
  3. 2026-06-10 13:20 UTCEPSS rescore
  4. 2026-06-02 20:11 UTCEPSS rescore
  5. 2026-06-02 20:11 UTCEPSS rescore
  6. 2026-06-01 13:50 UTCEPSS rescore
  7. 2026-06-01 13:50 UTCEPSS rescore
  8. 2026-05-31 22:29 UTCEPSS rescore
  9. 2026-05-31 22:29 UTCEPSS rescore
  10. 2026-05-28 13:43 UTCEPSS rescore
  11. 2026-05-28 13:43 UTCEPSS rescore
  12. 2026-05-26 07:17 UTCEPSS rescore
  13. 2026-05-26 07:17 UTCEPSS rescore
  14. 2026-05-24 16:48 UTCEPSS rescore
  15. 2026-05-23 07:52 UTCEG score recompute
  16. 2026-05-23 07:52 UTCGHSA enrichment

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCSchira4396/CVE-2020-25540
    First seen Oct 19, 2020

    ThinkAdmin CVE-2020-25540 poc

    Open source ↗
  • Exploit-DBEDB-48812
    First seen Sep 15, 2020

    ThinkAdmin 6 - Arbitrarily File Read

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-25540.yaml
    First seen Jan 1, 2020

    ThinkAdmin 6 - Local File Inclusion

    Open source ↗

Frequently asked(5)

What is CVE-2020-25540?
CVE-2020-25540 is a high vulnerability published on September 14, 2020. ThinkAdmin v6 is affected by a directory traversal vulnerability. An unauthorized attacker can read arbitrarily file on a remote server via GET request encode parameter.
When was CVE-2020-25540 disclosed?
CVE-2020-25540 was first published in the National Vulnerability Database on September 14, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-25540 actively exploited?
CVE-2020-25540 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-25540?
CVE-2020-25540 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.8.
How do I remediate CVE-2020-25540?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-25540, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-25540

Explore →

Is Your Infrastructure Affected by CVE-2020-25540?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.