Description
Emlog is an open source website building system. Prior to version 2.6.16, Emlog CMS Pro contains a blind SQL injection in User_Model::getUserDataByLogin(). The $account parameter is directly interpolated into SQL queries without any filtering. The vulnerability is reachable through the auth cookie validation path, where $username is extracted from the cookie and passed unfiltered into SQL — guarded only by an HMAC signature that requires AUTH_KEY to forge. This issue has been patched in version 2.6.16.
Published: 2026-09-04
Score: 4.9 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Emlog CMS Pro before version 2.6.16 contains a blind SQL injection in the function that retrieves user data. The vulnerability arises because the username extracted from the authentication cookie is concatenated directly into an SQL statement without sanitisation. The only guard is an HMAC signature that requires the server’s AUTH_KEY, so an attacker would need to forge the cookie or have the key. Successful exploitation could allow extraction or manipulation of database records, resulting in data disclosure or modification.

Affected Systems

The affected product is Emlog CMS Pro, version 2.6.15 and earlier. The issue is present in all builds that use the vulnerable User_Model module prior to the 2.6.16 release. No further vendor details are available beyond the emlog product.

Risk and Exploitability

The CVSS score of 4.9 indicates moderate severity. The vulnerability is a blind SQL injection, so exploitation requires iterative query timing or error analysis, which limits immediate impact. EPSS not available and the vulnerability is not listed in CISA KEV. Because forging the authentication cookie demands knowledge of the server’s AUTH_KEY, the risk to external attackers is low unless the key is compromised. Administrators should prioritize applying the 2.6.16 patch to eliminate the flaw.

Generated by OpenCVE AI on September 4, 2026 at 20:15 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Deploy the official Emlog CMS Pro 2.6.16 update or newer, which removes the vulnerable code.
  • If upgrading is not possible, generate a new, complex AUTH_KEY and then flush all session cookies for existing users to prevent reuse of compromised cookies.
  • Implement additional input validation around the $account parameter or refactor the query to use parameterised prepared statements.
  • Monitor database activity for anomalous queries that may indicate attempts to probe the injection point.

Generated by OpenCVE AI on September 4, 2026 at 20:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 21:45:00 +0000

Type Values Removed Values Added
First Time appeared Emlog
Emlog emlog
Vendors & Products Emlog
Emlog emlog

Fri, 04 Sep 2026 18:00:00 +0000

Type Values Removed Values Added
Description Emlog is an open source website building system. Prior to version 2.6.16, Emlog CMS Pro contains a blind SQL injection in User_Model::getUserDataByLogin(). The $account parameter is directly interpolated into SQL queries without any filtering. The vulnerability is reachable through the auth cookie validation path, where $username is extracted from the cookie and passed unfiltered into SQL — guarded only by an HMAC signature that requires AUTH_KEY to forge. This issue has been patched in version 2.6.16.
Title Emlog Blind SQL Injection via Authentication Cookie
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-04T17:46:58.174Z

Reserved: 2026-06-10T17:48:40.546Z

Link: CVE-2026-53756

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-04T18:17:52.350

Modified: 2026-09-04T18:17:52.350

Link: CVE-2026-53756

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T21:30:07Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')