# CVE-2023-46748: F5 BIG-IP Configuration Utility SQL Injection

> Authenticated attackers can execute arbitrary system commands via SQL injection in the BIG-IP Configuration utility.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 31 Oct 2023 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-9h42-3pgf-qjc8

## What is CVE-2023-46748?

CVE-2023-46748 is a high-severity SQL injection vulnerability in F5 Big-Ip Access Policy Manager, published on 26 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 versions which have reached End of Technical Support (EoTS) are not evaluated

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-46748?

It affects 20 products.


Products: F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Advanced Web Application Firewall, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Application Visibility and Reporting, F5 Big-Ip Automation Toolchain, F5 Big-Ip Carrier-Grade Nat, F5 Big-Ip Container Ingress Services, F5 Big-Ip Ddos Hybrid Defender, F5 Big-Ip Domain Name System, F5 Big-Ip Fraud Protection Services, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Ip Ssl Orchestrator, F5 Big-Ip Webaccelerator, F5 Big-Ip Websafe.

## How do I fix CVE-2023-46748?

No fix has been published for CVE-2023-46748 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 21 Nov 2023.

## Is CVE-2023-46748 being exploited?

Yes. Attackers have exploited CVE-2023-46748 in the wild since at least 31 Oct 2023.

## Other vulnerabilities in F5 Big-Ip Access Policy Manager

- [CVE-2023-46747](https://insights.sbomify.com/CVE-2023-46747/): F5 BIG-IP Configuration Utility Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-1388](https://insights.sbomify.com/CVE-2022-1388/): F5 BIG-IP Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2021-22986](https://insights.sbomify.com/CVE-2021-22986/): F5 BIG-IP and BIG-IQ Centralized Management iControl REST Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-22991](https://insights.sbomify.com/CVE-2021-22991/): F5 BIG-IP Traffic Management Microkernel Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2020-5902](https://insights.sbomify.com/CVE-2020-5902/): F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46748 and fix it if it is affected.

What it is: CVE-2023-46748 is a high-severity SQL injection vulnerability in F5 Big-Ip Access Policy Manager, published on 26 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-46748 in the wild since at least 31 Oct 2023.

Affected product: F5 Big-Ip Access Policy Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-46748/ (Markdown: https://insights.sbomify.com/CVE-2023-46748/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46748
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46748
- OSV: https://osv.dev/vulnerability/CVE-2023-46748

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-46748/
Summaries are generated and may contain mistakes; the official description above is the record.