CVE-2023-46748
SQLi in F5 Big-Ip Access Policy Manager 13.1.0 – 13.1.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-46748 is a high-severity SQL Injection (CWE-89) vulnerability in F5 Big-Ip Access Policy Manager. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 9% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
An authenticated SQL injection vulnerability tracked as CVE-2023-46748 affects the BIG-IP Configuration utility. The flaw, assigned CWE-89 and carrying a CVSS 3.1 score of 8.8, resides in F5 BIG-IP software and permits an attacker who already possesses valid credentials and network reachability to the management interface to execute arbitrary system commands.
An authenticated attacker with network access to the Configuration utility through the BIG-IP management port or self IP addresses can leverage the injection to run operating-system commands on the affected device. The attack requires no user interaction and can be performed remotely once the attacker has obtained valid credentials.
F5 has published remediation guidance under article K000137365, and the vulnerability appears in CISA’s Known Exploited Vulnerabilities catalog. A companion report notes that the issue has been observed in active exploit chains. The associated EPSS score has remained flat at 0.0435 since disclosure, indicating steady but not sharply increasing exploitation interest.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-50917
Vulnerability Data
An authenticated SQL injection vulnerability exists in the BIG-IP Configuration utility which may allow an authenticated attacker with network access to the Configuration utility through the BIG-IP management port and/or self IP addresses to execute arbitrary system commands. Note: Software…
more
versions which have reached End of Technical Support (EoTS) are not evaluated
- CWE(s)
- KEV Date Added
- 31 October 2023
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.5
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.