# CVE-2023-26213: Command injection in n/a

> An authenticated attacker can execute arbitrary OS commands on Barracuda CloudGen WAN Private Edge Gateway devices via a crafted HTTP request.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2023
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-m789-8jxv-f7m3

## What is CVE-2023-26213?

CVE-2023-26213 is a high-severity command injection vulnerability in n/a, published on 3 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

On Barracuda CloudGen WAN Private Edge Gateway devices before 8 webui-sdwan-1089-8.3.1-174141891, an OS command injection vulnerability exists in /ajax/update_certificate - a crafted HTTP request allows an authenticated attacker to execute arbitrary commands. For example, a name field can contain :password and a password field can contain shell metacharacters.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 7 products.


Products: Barracuda T100b Firmware, Barracuda T193a Firmware, Barracuda T200c Firmware, Barracuda T400c Firmware, Barracuda T600d Firmware, Barracuda T900b Firmware, Barracuda T93a Firmware.

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

No fix has been published for CVE-2023-26213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-26213 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26213 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-26213 is a high-severity command injection vulnerability in n/a, published on 3 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26213 exists.

Affected product: n/a. 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-26213/ (Markdown: https://insights.sbomify.com/CVE-2023-26213/index.md)
```

## Sources

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

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