Skip to content
Fencer Intel
medium 6.5

CVE-2020-13945 json

In Apache APISIX, the user enabled the Admin API and deleted the Admin API access IP restriction rules.

published 5y ago modified 2mo ago also BIT-apisix-2020-13945 , EUVD-2020-6132

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
73.6%
EPSS 73.6% chance of exploitation in 30 days, percentile 99.4%
public exploits
1
Metasploit, plus a Nuclei check

Summary

In Apache APISIX, the user enabled the Admin API and deleted the Admin API access IP restriction rules. Eventually, the default token is allowed to access APISIX management data. This affects versions 1.2, 1.3, 1.4, 1.5.

Patch / fix

Is CVE-2020-13945 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 Fencer

Timeline

  1. First public exploit (Metasploit exploit/multi/http/apache_apisix_api_default_token_rce)
  2. Published

Exploit prediction

73.59% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami apisix
>=1.2.0, <1.5.1
1.5.1

Affected products

  • Apache Software Foundation Apache APISIX

References

Sources

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.