# CVE-2025-34334: AudioCodes Fax/IVR Appliance <= 2.6.23 Authenticated Command Injection via TestFax.php & LPE

> Authenticated attackers can inject commands into fax test parameters to execute arbitrary code with SYSTEM privileges on AudioCodes Fax/IVR appliances.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-8fqr-64hx-fpfp

## What is CVE-2025-34334?

CVE-2025-34334 is a high-severity command injection vulnerability in AudioCodes Fax/IVR Appliance, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AudioCodes Fax Server and Auto-Attendant IVR appliances versions up to and including 2.6.23 are vulnerable to an authenticated command injection in the fax test functionality implemented by AudioCodes_files/TestFax.php. When a fax "send" test is requested, the application builds a faxsender command line using attacker-supplied parameters and passes it to GlobalUtils::RunBatchFile without proper validation or shell-argument sanitization. The resulting batch file is written into a temporary run directory and then executed via a backend service that runs as NT AUTHORITY\\SYSTEM. An authenticated attacker with access to the fax test interface can craft parameter values that inject additional shell commands into the generated batch file, leading to arbitrary command execution with SYSTEM privileges. In addition, because the generated batch files reside in a location with overly permissive file system permissions, a local low-privilege user on the server can modify pending batch files to achieve the same elevation.

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

## Which versions are affected by CVE-2025-34334?

It affects 2 products.


Products: Audiocodes Fax Server, Audiocodes Interactive Voice Response.

## How do I fix CVE-2025-34334?

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

## Is CVE-2025-34334 being exploited?

There is no known exploitation of CVE-2025-34334 in the wild and no public exploit code.

## Other vulnerabilities in AudioCodes Fax/IVR Appliance

- [CVE-2025-34328](https://insights.sbomify.com/CVE-2025-34328/): AudioCodes Fax/IVR Appliance <= 2.6.23 Unauthenticated File Upload RCE via ajaxScript.php (critical 9.3)
- [CVE-2025-34329](https://insights.sbomify.com/CVE-2025-34329/): AudioCodes Fax/IVR Appliance <= 2.6.23 Unauthenticated Backup Upload RCE via ajaxBackupUploadFile.php (critical 9.3)
- [CVE-2025-34331](https://insights.sbomify.com/CVE-2025-34331/): AudioCodes Fax/IVR Appliance <= 2.6.23 Unauthenticated File Read via download.php (high 8.7)
- [CVE-2025-34335](https://insights.sbomify.com/CVE-2025-34335/): AudioCodes Fax/IVR Appliance <= 2.6.23 Authenticated Command Injection via ActivateLicense.php (high 8.7)
- [CVE-2025-34332](https://insights.sbomify.com/CVE-2025-34332/): AudioCodes Fax/IVR Appliance <= 2.6.23 Insecure Service Control Scripts LPE (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34334 and fix it if it is affected.

What it is: CVE-2025-34334 is a high-severity command injection vulnerability in AudioCodes Fax/IVR Appliance, published on 19 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34334 in the wild and no public exploit code.

Affected product: AudioCodes Fax/IVR Appliance. 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-2025-34334/ (Markdown: https://insights.sbomify.com/CVE-2025-34334/index.md)
```

## Sources

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

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