How severe is CVE-2021-45232?

CVE-2021-45232 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-45232?

Affected package information for CVE-2021-45232 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2021-45232?

No fixed version has been published for CVE-2021-45232 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2021-45232 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2021-45232, including 4 in-the-wild exploitations 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-2021-45232?

CVE-2021-45232 has an EPSS (Exploit Prediction Scoring System) score of 93.7%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for CVE-2021-45232?

A Nuclei detection template exists for CVE-2021-45232, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2021-45232 published, and has it been updated?

CVE-2021-45232 was published on December 27, 2021 and was last updated on March 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2021-45232

CRITICAL

Also known asBIT-apisix_dashboard-2021-45232

Published

Dec 27, 2021

Updated

Mar 14, 2026

Affected

0 pkgs

Patched

None yet

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

93.7%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

In Apache APISIX Dashboard before 2.10.1, the Manager API uses two frameworks and introduces framework droplet on the basis of framework gin, all APIs and authentication middleware are developed based on framework droplet, but some API directly use the interface of framework gin thus bypassing the authentication.

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.

In Apache APISIX Dashboard before 2.10.1, the Manager API uses two frame…

github.comGithubDec 2021

In Apache APISIX Dashboard before 2.10.1, the Manager API uses two frame…

github.comGithubJan 2022

In Apache APISIX Dashboard before 2.10.1, the Manager API uses two frame…

github.comGithubDec 2021

In Apache APISIX Dashboard before 2.10.1, the Manager API uses two frame…

github.comGithubMay 2022

Frequently Asked Questions

In Apache APISIX Dashboard before 2.10.1, the Manager API uses two frameworks and introduces framework `droplet` on the basis of framework `gin`, all APIs and authentication middleware are developed based on framework `droplet`, but some API directly use the interface of framework `gin` thus bypassing the authentication.

O3 Security · Impact-Aware SCA

Is CVE-2021-45232 in your stack?

O3 detects CVE-2021-45232 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works