CVE-2025-61678
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 prior to 16.0.92 for FreePBX 16 and versions prior to 17.0.6 for FreePBX 17, the Endpoint Manager module contains an authenticated arbitrary file upload vulnerability affecting the fwbrand parameter. The fwbrand parameter allows an attacker to change the file path. Combined, these issues can result in a webshell being uploaded. Authentication with a known username is required to exploit this vulnerability. Successful exploitation allows authenticated users to upload arbitrary files to attacker-controlled paths on the server, potentially leading to remote code execution. This issue has been patched in version 16.0.92 for FreePBX 16 and version 17.0.6 for FreePBX 17.
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 prior to 16.0.92 (FPBX16) and 17.0.6 (FPBX17) contain an authenticated arbitrary file upload vulnerability. The fwbrand parameter allows path manipulation, enabling attackers to upload arbitrary files including webshells to attacker-controlled paths, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 FreePBX Endpoint Manager installation and versionCheck the Endpoint Manager module version via FreePBX admin interface (Admin > Module Administration) or by examining the module's version file if accessible on the filesystemAffected if The installed version is below 16.0.92 for FreePBX 16 systems or below 17.0.6 for FreePBX 17 systems
-
Verify administrative access is availableConfirm that user accounts with administrative privileges exist in FreePBX (Admin > User Management). An attacker requires valid credentials to exploit this vulnerability.Affected if Administrative or high-privilege credentials are present and could be compromised
-
Check for suspicious files in web root directoriesSearch for unexpected PHP files, especially webshells, in directories writable by the web server user. Common paths include /var/www/html/ and any custom brand upload directories.Affected if Unexpected PHP files or webshell-like code is found in web-accessible directories, particularly in brand upload paths
-
Review web server access logs for fwbrand parameter exploitationExamine web server access logs (typically /var/log/httpd/ or /var/log/nginx/) for requests containing 'fwbrand' parameter with path traversal patterns (e.g., ../) or unusual file extensionsAffected if Log entries show file upload attempts via fwbrand parameter with manipulated paths
You are affected if FreePBX Endpoint Manager version is below 16.0.92 (FPBX16) or below 17.0.6 (FPBX17), administrative access exists, and either suspicious files are present or exploitation attempts appear in logs.
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 · scopedUpgrade FreePBX Endpoint Manager to version 16.0.92 or later for FreePBX 16, or version 17.0.6 or later for FreePBX 17. Restrict administrative access and enforce strong credentials as a defense-in-depth measure.
FreePBX 16: upgrade Endpoint Manager to 16.0.92; FreePBX 17: upgrade Endpoint Manager to 17.0.6
- 1. Back up the FreePBX system before performing any updates
- 2. Access the FreePBX administration interface
- 3. Navigate to Admin > Module Admin
- 4. Check for available updates for the Endpoint Manager module
- 5. Update the Endpoint Manager module to version 16.0.92 (for FreePBX 16) or version 17.0.6 (for FreePBX 17)
- 6. Alternatively, use the command line: fwconsole ma upgrade endpoint
- 7. After upgrading, verify the fwbrand parameter behavior has been restricted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61678 — 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-61678 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