# CVE-2025-34335: AudioCodes Fax/IVR Appliance <= 2.6.23 Authenticated Command Injection via ActivateLicense.php

> Authenticated attackers can execute arbitrary system commands via crafted license filenames in 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:** 21 Nov 2025
- **Also known as:** GHSA-38qx-8m29-gqjv

## What is CVE-2025-34335?

CVE-2025-34335 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 expose an authenticated command injection vulnerability in the license activation workflow handled by AudioCodes_files/ActivateLicense.php. When a license file is uploaded, the application derives a new filename by combining a generated base name with the attacker-controlled extension portion of the original upload name, then constructs a command line for fax_server_lic_cmdline.exe that includes this path. The extension value is incorporated into the command string without input validation, escaping, or proper argument quotation before being passed to exec(). An authenticated user with access to the license upload interface can supply a specially crafted filename whose extension injects additional shell metacharacters, causing arbitrary commands to be executed as NT AUTHORITY\\SYSTEM.

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

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

It affects 2 products.


Products: Audiocodes Fax Server, Audiocodes Interactive Voice Response.

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

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

## Is CVE-2025-34335 being exploited?

There is no known exploitation of CVE-2025-34335 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-34334](https://insights.sbomify.com/CVE-2025-34334/): AudioCodes Fax/IVR Appliance <= 2.6.23 Authenticated Command Injection via TestFax.php & LPE (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-34335 and fix it if it is affected.

What it is: CVE-2025-34335 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-34335 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-34335/ (Markdown: https://insights.sbomify.com/CVE-2025-34335/index.md)
```

## Sources

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

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