CVE-2026-44239
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 is an open source IP PBX. Prior to 16.0.22 and 17.0.5, the Dashboard module's getcontent AJAX handler includes PHP files based on user-supplied input without path sanitization. The $_REQUEST['rawname'] parameter is concatenated into an include() call with a .class.php suffix, allowing path traversal via ../ sequences to include arbitrary .class.php files from the filesystem. The included file's PHP code executes before the subsequent class instantiation error occurs. This vulnerability is fixed in 16.0.22 and 17.0.5.
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 confidenceA path traversal vulnerability in FreePBX's Dashboard module allows remote attackers to execute arbitrary PHP code by manipulating the 'rawname' parameter in the getcontent AJAX handler. The parameter is directly concatenated into an include() call with a .class.php suffix, enabling attackers to use ../ sequences to traverse directories and include any .class.php file from the filesystem, which executes before the subsequent class instantiation error occurs.
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< 16.0.22>= 17.0, < 17.0.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 FreePBX installation and versionRun 'fwconsole ma list' or check /etc/freepbx.conf for the version string. Alternatively, look at the admin interface footer which displays the version.Affected if The installed version is < 16.0.22 or >= 17.0.0 and < 17.0.5
-
Verify Dashboard module is installedRun 'fwconsole ma list | grep dashboard' to check if the Dashboard module is present and enabled.Affected if Dashboard module is installed and enabled (the vulnerable AJAX handler exists)
-
Check if getcontent AJAX endpoint is accessibleInspect the Dashboard module files under /var/www/html/admin/modules/dashboard/ for the getcontent AJAX handler that processes the 'rawname' parameter. Look for files containing 'getcontent' and 'rawname' references.Affected if The getcontent handler processes the rawname parameter directly into an include() call with .class.php suffix
-
Test for path traversal in rawname parameterReview web server logs or access the AJAX endpoint with a crafted request containing '../' sequences in the rawname parameter (e.g., ?module=getcontent&rawname=../../etc/passwd). Note: Only perform this in authorized test environments.Affected if The application accepts path traversal sequences and attempts to include files outside the intended directory
-
Confirm .class.php suffix is appended to user inputExamine the vulnerable code in the Dashboard module to verify that the rawname parameter is directly concatenated with '.class.php' in the include() statement without sanitization.Affected if The code appends .class.php to unsanitized user input from the rawname parameter
You are affected if FreePBX version is < 16.0.22 or between 17.0.0 and 17.0.5 AND the Dashboard module is installed, as the vulnerable getcontent handler processes unsanitized path traversal in the rawname parameter.
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 · scoped16.0.2217.0.5
Upgrade to FreePBX 16.0.22 or 17.0.5 to obtain the patched version. If immediate upgrading is not feasible, restrict network access to the Dashboard module's AJAX endpoints and implement web application firewall rules to block path traversal patterns in the 'rawname' parameter.
FreePBX 16.0.22+ or 17.0.5+ (depending on your major version branch)
- 1. Identify current FreePBX version by checking the FreePBX admin dashboard or running 'fwconsole ma list' command
- 2. Create a complete backup of the FreePBX system including all configurations, voicemail, recordings, and database
- 3. If running FreePBX 16.x (< 16.0.22): Upgrade to version 16.0.22 or later using the FreePBX module admin or fwconsole command
- 4. If running FreePBX 17.x (>= 17.0 and < 17.0.5): Upgrade to version 17.0.5 or later using the FreePBX module admin or fwconsole command
- 5. After upgrade, verify the Dashboard module is updated and the getcontent AJAX handler no longer accepts unsanitized user input
- 6. Test that FreePBX core functionality (calls, extensions, routing) continues to work correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.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 $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44239 — 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-2026-44239 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