CVE-2025-64328
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 · uneditedFreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. In versions 17.0.2.36 and above before 17.0.3, the filestore module within the Administrative interface is vulnerable to a post-authentication command injection by an authenticated known user via the testconnection -> check_ssh_connect() function. An attacker can leverage this vulnerability to obtain remote access to the system as an asterisk user. This issue is fixed in version 17.0.3.
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 confidenceFreePBX Endpoint Manager versions 17.0.2.36 through 17.0.2.x contain a post-authentication command injection vulnerability in the filestore module's testconnection/check_ssh_connect() function. An authenticated user with known credentials can inject arbitrary shell commands through this function, executing them as the asterisk system user to obtain remote access.
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>= 17.0.2.36, < 17.0.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Determine the installed Endpoint Manager versionRun the command: fwconsole ma list | grep endpoint or access Admin > Module Admin in the FreePBX web interface to view the installed version of Endpoint Manager / Sangoma FilestoreAffected if The displayed version is 17.0.2.36 through 17.0.2.x (any version below 17.0.3)
-
Confirm the filestore module is installedRun: fwconsole ma list | grep filestore or check the FreePBX web interface under Admin > Module Admin for the Filestore moduleAffected if The filestore module appears in the list of installed modules
-
Verify SSH storage configuration existsNavigate to the Endpoint Manager settings in the web interface (Settings > Endpoint Manager > File Store) or inspect the database: mysql -e 'select * from freepbx filestore;' 2>/dev/null to see if any SSH/remote storage configurations are definedAffected if SSH or remote storage connections are configured in the filestore module
-
Check for administrative access to the moduleReview user accounts in FreePBX (Admin > User Management) and verify which accounts have access to the Endpoint Manager or filestore configuration pagesAffected if Any valid administrative credentials exist that can access the filestore configuration
You are affected if your Endpoint Manager filestore version is 17.0.2.36 or higher but lower than 17.0.3, the filestore module is installed, and an attacker can obtain valid admin credentials to access the filestore configuration interface.
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 · scoped17.0.3
Upgrade FreePBX Endpoint Manager to version 17.0.3 or later. Until patched, limit administrative access to trusted users only and monitor for unauthorized access.
FreePBX 17.0.3 or later
- 1. Before performing any upgrade, create a complete backup of your FreePBX system including all configurations, recordings, and the asterisk database.
- 2. Ensure you have tested backup restoration procedures in a non-production environment.
- 3. Access the FreePBX Administrative interface with valid credentials.
- 4. Navigate to the module administration or use the built-in upgrade mechanism to update to version 17.0.3 or later.
- 5. Alternatively, from the command line as root, run the FreePBX module update commands to upgrade the filestore module: fwconsole ma upgrade filestore
- 6. After upgrading, verify the filestore module version is 17.0.3 or higher.
- 7. Test the testconnection function to confirm the vulnerability is remediated.
- 8. Review user accounts with access to the filestore module and ensure only necessary personnel have administrative access.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64328 — 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-64328 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