CVE-2025-34328
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAudioCodes Fax Server and Auto-Attendant IVR appliances versions up to and including 2.6.23 include a web administration component (F2MAdmin) that exposes an unauthenticated script-management endpoint at AudioCodes_files/utils/IVR/diagram/ajaxScript.php. The saveScript action writes attacker-supplied data directly to a server-side file path under the privileges of the web service account, which runs as NT AUTHORITY\\SYSTEM on Windows deployments. A remote, unauthenticated attacker can write arbitrary files into the product’s web-accessible directory structure and subsequently execute them.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAudioCodes Fax Server and IVR appliances up to version 2.6.23 contain an unauthenticated file-write vulnerability in the F2MAdmin web component's ajaxScript.php endpoint. The saveScript action permits a remote, unauthenticated attacker to write arbitrary files to the web-accessible directory, which are subsequently executable. The web service runs as NT AUTHORITY\SYSTEM, providing full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.6.23<= 2.6.23CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify product and versionLocate the installed version of AudioCodes Fax Server or AudioCodes Interactive Voice Response (IVR) via the administrative interface, system information, or installed programs list.Affected if The product is AudioCodes Fax Server or IVR with version 2.6.23 or lower.
-
Locate F2MAdmin web componentSearch the web server directories for the F2MAdmin folder and specifically the ajaxScript.php file.Affected if The ajaxScript.php file exists in a web-accessible directory under the F2MAdmin component.
-
Verify F2MAdmin is exposedDetermine if the F2MAdmin web interface is accessible from the network by attempting to access the URL or reviewing firewall/network configurations.Affected if The F2MAdmin endpoint is reachable over the network without authentication.
-
Confirm saveScript action is enabledInspect the ajaxScript.php configuration or attempt a request to the saveScript action endpoint to verify it accepts unauthenticated requests.Affected if The saveScript action accepts requests without requiring authentication.
A user is affected if they are running AudioCodes Fax Server or IVR version 2.6.23 or lower with the F2MAdmin web component exposed to the network and the ajaxScript.php saveScript action enabled and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately restrict network access to the F2MAdmin web interface using firewall rules or disable the component if unnecessary. Monitor for indicators of compromise and apply vendor-supplied patches when available.
Version greater than 2.6.23 (contact AudioCodes for exact patched release)
- 1. Identify the current version of AudioCodes Fax Server or Interactive Voice Response (IVR) by accessing the web administration interface or checking system information.
- 2. Contact AudioCodes technical support or visit the official AudioCodes support portal to obtain the patched version that addresses CVE-2025-34328.
- 3. Download the updated firmware/software version from AudioCodes official channels.
- 4. Follow AudioCodes documented upgrade procedures, ensuring to backup configuration settings before applying the update.
- 5. After upgrading, verify that the vulnerable endpoint (AudioCodes_files/utils/IVR/diagram/ajaxScript.php) is either removed, patched, or requires authentication.
- 6. Confirm the new version is running and the vulnerability is remediated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data