# CVE-2025-34332: AudioCodes Fax/IVR Appliance <= 2.6.23 Insecure Service Control Scripts LPE

> Local attackers can escalate privileges to SYSTEM by modifying writable service control scripts executed by the web administration component.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-x8c7-9v8r-m3jq

## What is CVE-2025-34332?

CVE-2025-34332 is a high-severity vulnerability in AudioCodes Fax/IVR Appliance, published on 19 Nov 2025. It can only be exploited from the same machine or local 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 include a web administration component that controls back-end Windows services using helper batch scripts located under C:\\F2MAdmin\\F2E\\AudioCodes_files\\utils\\Services. When certain service actions are requested through ajaxPost.php, these scripts are invoked by PHP using system() under the NT AUTHORITY\\SYSTEM account. The batch files in this directory are writable by any authenticated local user due to overly permissive ACLs, allowing them to replace script contents with arbitrary commands. On the next service start/stop operation, the modified script is executed as SYSTEM, enabling elevation of local privileges.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 2 products.


Products: Audiocodes Fax Server, Audiocodes Interactive Voice Response.

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

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

## Is CVE-2025-34332 being exploited?

There is no known exploitation of CVE-2025-34332 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-34335](https://insights.sbomify.com/CVE-2025-34335/): AudioCodes Fax/IVR Appliance <= 2.6.23 Authenticated Command Injection via ActivateLicense.php (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34332 is a high-severity vulnerability in AudioCodes Fax/IVR Appliance, published on 19 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34332 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-34332/ (Markdown: https://insights.sbomify.com/CVE-2025-34332/index.md)
```

## Sources

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

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