CVE-2026-27395
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 · uneditedUnauthenticated Privilege Escalation in Support Board < 3.8.9 versions.
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 confidenceUnauthenticated privilege escalation vulnerability in Support Board versions prior to 3.8.9 allows remote attackers to gain elevated privileges without authentication. The CVSS 9.8 score indicates trivial exploitability with complete system compromise potential.
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
- 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.
-
Confirm Support Board is deployedIdentify whether the Support Board help desk application is installed in your environment. Check web server directories, application inventories, or software asset records for 'Support Board' or related PHP-based help desk software.Affected if Support Board software is present in the environment
-
Locate the installed versionAccess the Support Board administration panel and navigate to Settings > System, or check the /sb-config.php file, version.php file, or the footer of the application interface for the version number.Affected if The version displayed is lower than 3.8.9 or cannot be determined (unknown versions should be treated as vulnerable)
-
Compare version to affected rangeReview the identified version number against the affected range: all versions prior to 3.8.9. Common version formats may appear as 3.x.x or earlier.Affected if The installed version is 3.8.8, 3.8.7, 3.8.0, 3.7.x, 3.6.x, or any version number below 3.8.9
-
Verify network accessibilityDetermine if the Support Board application is accessible over the network. Check firewall rules, web server configuration, and whether the application is exposed to the internet or untrusted internal networks.Affected if The application is network-accessible without strong authentication gates, increasing the risk of unauthenticated exploitation
You are affected if Support Board version 3.8.9 or later is not installed; the unauthenticated privilege escalation applies to all prior versions regardless of configuration.
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 Support Board to version 3.8.9 or later to remediate the vulnerability. If immediate upgrade is not possible, restrict network access to the application and monitor for unauthorized admin access.
Support Board 3.8.9 or later
- Upgrade Support Board to version 3.8.9 or later to remediate the unauthenticated privilege escalation vulnerability (CWE-266)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27395 — 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-27395 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