CVE-2026-28284
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 versions 16.0.10 and 17.0.5, the FreePBX logfiles module contains several authenticated SQL injection vulnerabilities. This issue has been patched in versions 16.0.10 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 · moderate confidenceFreePBX IP PBX software contains authenticated SQL injection vulnerabilities in its logfiles module prior to versions 16.0.10 and 17.0.5. An attacker with valid credentials can exploit this to manipulate database queries, potentially exfiltrating, modifying, or deleting data.
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, < 16.0.10>= 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 versionAccess the FreePBX admin dashboard and navigate to Admin > System Admin > Version, or run 'fwconsole ma list' at the command line to list installed modules and versions.Affected if The installed version falls within the range >= 16.0.0 and < 16.0.10, or >= 17.0.0 and < 17.0.5.
-
Confirm logfiles module is installedRun 'fwconsole ma list | grep logfiles' or check the module administration page in the FreePBX GUI to verify the logfiles module is present and enabled.Affected if The logfiles module is installed and enabled on the system.
-
Verify administrative access existsReview user accounts in FreePBX under Admin > User Management to determine if valid credentials exist for users with access to the logfiles module functionality.Affected if At least one valid user account with privileges to access the logfiles module exists in the system.
The environment is affected if FreePBX version is 16.0.0-16.0.9 or 17.0.0-17.0.4, the logfiles module is enabled, and valid credentials exist for a user who can access that module.
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.1017.0.5
Upgrade FreePBX to version 16.0.10 or 17.0.5 or later. Additionally, apply least-privilege principles to user accounts and restrict network access to administrative interfaces.
FreePBX 16.0.10 (for 16.x branch) or FreePBX 17.0.5 (for 17.x branch)
- Backup your FreePBX system and database before performing any upgrade
- Verify your current FreePBX version (16.x or 17.x branch) using the admin interface or CLI
- For FreePBX 16.x users: Upgrade to version 16.0.10 or later
- For FreePBX 17.x users: Upgrade to version 17.0.5 or later
- Apply the upgrade through your system package manager or FreePBX online support module
- Restart affected services if required after upgrade
- Verify the logfiles module is now running the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28284 — 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-28284 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