dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-8851

HIGH · 8.1 CVSS v3.1 Published 2026-05-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
SOGo versions 5.12.7 and prior contains a SQL injection vulnerability in the Access Control List management functionality that allows authenticated users to extract arbitrary data from the database by injecting SQL subqueries through the uid parameter of the addUserInAcls endpoint. Attackers can inject malicious SQL code to write extracted data into the sogo_acl table and retrieve it through the /acls API, establishing an out-of-band data exfiltration channel.

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 confidence

SOGo versions 5.12.7 and prior contain a SQL injection vulnerability in the Access Control List management functionality. Authenticated attackers can inject SQL subqueries through the uid parameter of the addUserInAcls endpoint, allowing arbitrary data extraction from the database. The attacker writes exfiltrated data to the sogo_acl table and retrieves it via the /acls API, creating an out-of-band data exfiltration channel.

MitigationUpgrade to a version newer than 5.12.7, or implement proper input validation and parameterized queries in the addUserInAcls endpoint to prevent SQL injection.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SOGo version
    Run 'sogo-tool --version' or check the package manager (dpkg -l | grep sogo, rpm -qa | grep sogo) to find the installed SOGo version
    Affected if The installed version is 5.12.7 or any version prior to 5.12.7
  2. Verify ACL management is enabled
    Inspect SOGo configuration files (typically /etc/sogo/sogo.conf or /etc/sogo/sogo.conf.d/) for ACL-related settings - look for 'SOGoACLs' or 'Acls' configuration options that enable the ACL feature
    Affected if ACL management functionality is enabled in the SOGo configuration
  3. Confirm API endpoint accessibility
    Check if the /SOGo/acl API endpoint is exposed by reviewing web server configuration (Apache/Nginx) or testing access to http(s)://<server>/SOGo/acl
    Affected if The ACL API endpoint (/SOGo/acl or /acls) is accessible without additional authentication beyond basic SOGo login
  4. Review access logs for exploitation attempts
    Examine web server access logs (Apache access_log, Nginx access.log) for suspicious requests to addUserInAcls endpoint with unusual uid parameter values containing SQL syntax (SELECT, UNION, subqueries)
    Affected if Log entries show requests to addUserInAcls or similar endpoints with SQL injection patterns in the uid parameter

A user is affected if SOGo version 5.12.7 or earlier is installed, ACL management is enabled, and the ACL API endpoint is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version newer than 5.12.7, or implement proper input validation and parameterized queries in the addUserInAcls endpoint to prevent SQL injection.

Recommended fix Moderate confidence

SOGo 5.12.8 or later stable release

  1. 1. Identify the currently installed SOGo version by checking the package manager or running 'sogo --version'
  2. 2. Backup the current SOGo configuration and database before proceeding with any upgrade
  3. 3. Upgrade SOGo to the latest stable release (version 5.12.8 or later, as 5.12.7 is the last vulnerable version)
  4. 4. For Debian/Ubuntu systems: run 'apt update && apt install sogo' or 'apt install sogo=latest' to pull the newest version
  5. 5. For RHEL/CentOS systems: run 'yum update sogo' or 'dnf update sogo'
  6. 6. Verify the upgrade was successful by checking the installed version
  7. 7. Restart the SOGo service: 'systemctl restart sogo' or 'service sogo restart'
  8. 8. Test the ACL management functionality to ensure the application is working correctly post-upgrade
Caveat Review SOGo release notes for version 5.12.8+ to check for any configuration or feature changes that may require adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8851 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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