# CVE-2025-34329: AudioCodes Fax/IVR Appliance <= 2.6.23 Unauthenticated Backup Upload RCE via ajaxBackupUploadFile.php

> Remote attackers can upload malicious files to the unauthenticated backup endpoint, leading to arbitrary code execution with SYSTEM privileges on AudioCodes appliances.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-x988-43fg-2vcq

## What is CVE-2025-34329?

CVE-2025-34329 is a critical vulnerability in AudioCodes Fax/IVR Appliance, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, 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 unauthenticated backup upload endpoint at AudioCodes_files/ajaxBackupUploadFile.php in the F2MAdmin web interface. The script derives a backup folder path from application configuration, creates the directory if it does not exist, and then moves an uploaded file to that location using the attacker-controlled filename, without any authentication, authorization, or file-type validation. On default Windows deployments where the backup directory resolves to the system drive, a remote attacker can upload web server or interpreter configuration files that cause a log file or other server-controlled resource to be treated as executable code. This allows subsequent HTTP requests to trigger arbitrary command execution under the web server account, which runs as NT AUTHORITY\\SYSTEM.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 2 products.


Products: Audiocodes Fax Server, Audiocodes Interactive Voice Response.

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

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

## Is CVE-2025-34329 being exploited?

There is no known exploitation of CVE-2025-34329 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-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-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-34329 and fix it if it is affected.

What it is: CVE-2025-34329 is a critical vulnerability in AudioCodes Fax/IVR Appliance, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34329 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-34329/ (Markdown: https://insights.sbomify.com/CVE-2025-34329/index.md)
```

## Sources

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

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