CVE
SOGo SQL injection in SQLSource contact lookup
Only affects SOGo before 5.12.13 using SQLSource contact lookup on a SQL-backed address book on MySQL or MariaDB. Fixed in 5.12.13.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 5.12.13
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. SOGo before 5.12.13 with SQLSource contact lookup A SQL-backed address book path on MySQL or MariaDB
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Alinto SOGo has an SQL injection flaw in its SQLSource contact lookup that lets a logged-in user, reached remotely over the network, run SQL through a specially crafted object name. On SQL-backed address books using MySQL or MariaDB, an attacker can use UNION or boolean-based queries to read the user-source table, including password hashes.
Original description
Alinto SOGo before 5.12.13 contains an SQL injection vulnerability in SQLSource contact lookup that allows authenticated users to inject SQL by placing a backslash before a quote in the object name. Attackers can send requests under a SQL-backed address book path on MySQL or MariaDB to perform UNION or boolean-based reads of the user-source table, including password hashes.
Who should check
Teams running Alinto SOGo before 5.12.13 with SQL-backed (SQLSource) address books on MySQL or MariaDB
“Affecting sogo >= 0, < 5.12.13”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
SOGo before 5.12.13 with SQLSource contact lookup A SQL-backed address book path on MySQL or MariaDBUpgrade to a fixed version: 5.12.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130066 (Alinto SOGo before 5.12.13 SQL Injection via SQLSource Contact Lookup), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130066 (entry last updated 2026-11-16):
Affected:
- Alinto sogo: fixed in 5.12.13
Fixed versions: 5.12.13.
Conditions (all must be true for the bug to be hit):
- SOGo before 5.12.13 with SQLSource contact lookup (source: https://www.vulncheck.com/advisories/alinto-sogo-before-5.12.13-sql-injection-via-sqlsource-contact-lookup)
- A SQL-backed address book path on MySQL or MariaDB (source: https://www.vulncheck.com/advisories/alinto-sogo-before-5.12.13-sql-injection-via-sqlsource-contact-lookup)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130066 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130066 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Alinto/sogo/releases/tag/SOGo-5.12.13
- https://github.com/Alinto/sogo/commit/03ac106c2160bde2640b0400a77a805f8969acd8
- https://github.com/Alinto/sogo/commit/328c96cdd62acbb162eae4d0da99c3d1926d5e63
- https://github.com/Alinto/sogo/blob/SOGo-5.12.12/SoObjects/SOGo/SQLSource.m#L579-L666
- https://www.vulncheck.com/advisories/alinto-sogo-before-5.12.13-sql-injection-via-sqlsource-contact-lookup
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130066
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130066"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Alinto sogo
fixed in 5.12.13
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Advisory
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130066
Is CVE-2026-130066 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The SQLSource contact lookup in SOGo is injectable, so requests sent under a SQL-backed address book path can read the user-source table through UNION or boolean-based SQL injection, including password hashes.Source: vulncheck.com
Which versions are affected by CVE-2026-130066?
sogo: before 5.12.13.Source: cve.now feed data
Am I affected, and how do I check?
Versions of Alinto SOGo before 5.12.13 that use SQLSource contact lookup with a SQL-backed address book on MySQL or MariaDB are affected. To check a setup, look at the installed SOGo version and whether SQLSource address books are configured on MySQL or MariaDB.Source: vulncheck.com
How do I fix CVE-2026-130066?
Upgrade SOGo to 5.12.13, which is the fixed version listed for this vulnerability.Source: vulncheck.com