CVE-2024-20340
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- No fix version is held. The CNA's first reference is the place to look: sec.cloudapps.cisco.com
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software, formerly Firepower Management Center Software, could allow an authenticated, remote attacker to perform an SQL injection attack against an affected device. To exploit this vulnerability, an attacker must have a valid account on the device with the role of Security Approver, Intrusion Admin, Access Admin, or Network Admin. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP request to the web-based management interface of an affected device. A successful exploit could allow the attacker to read the contents of databases on the affected device and also obtain limited read access to the underlying operating system.
- weakness
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- affected
- Cisco Secure Firewall Management Center (FMC)
- published ranges
- cisco secure firewall management center 7.0.0; cisco secure firewall management center 7.0.0.1; cisco secure firewall management center 7.0.1; cisco secure firewall management center 7.0.1.1; and 35 more on the CVE page
- fixed in
- No fix version in held sources.
- severity
- 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- assigned by
- cisco
- published
- 2024-10-23
check us sec.cloudapps.cisco.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 24 Oct 2024 | 0.00045 | |
| 2 Nov 2024 | 0.00058 | |
| 17 Mar 2025 | 0.00037 | scoring model v2025.03.14 |
| 19 Mar 2025 | 0.00047 | |
| 27 Mar 2026 | 0.00193 | |
| 15 Jun 2026 | 0.00448 | scoring model v2026.06.15 |
| 30 Jul 2026 | 0.00455 | |
| 2 Aug 2026 | 0.00451 |
27 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-08-02 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-20340', '2026-11-01T23:59:59.999999Z', now());