CVE-2026-18110 Vulnerability Analysis & Exploit Details

CVE-2026-18110
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-18110 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-18110 Details

Status: Analyzed

Last updated: 🕕 22 Sep 2026, 18:17 UTC
Originally published on: 🕔 15 Sep 2026, 17:17 UTC

Time between publication and last update: 7 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2026-18110 Vulnerability Summary

CVE-2026-18110: Concrete CMS 9 (9.0.0 through 9.5.2) does not perform an authorization check on the user selector autocomplete endpoint (/ccm/system/user/autocomplete), which backs the "Preview as User" panel and other user-selector components. The endpoint validates only a CSRF-style access token that is bound to the selector's display options rather than to the caller's identity or permissions, and that token is issued to anonymous visitors because the selector renders without an authorization check. Because an empty query resolves to a match-all filter, an unauthenticated attacker can submit an empty search and paginate the results to enumerate every backend account, disclosing the internal user ID, username, and email address of all administrative users, including the super-administrator (user ID 1). No password hashes or session material are disclosed The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 8.7 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N. Thanks thirtythree and YesWeHack for reporting.

Assessing the Risk of CVE-2026-18110

Access Complexity Graph

The exploitability of CVE-2026-18110 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-18110

With low attack complexity and no required privileges, CVE-2026-18110 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-18110, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-18110, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-18110 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-18110 poses no threat to data integrity.
  • Availability: None
    CVE-2026-18110 does not impact system availability.

CVE-2026-18110 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:a:concretecms:concrete_cms:9.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.7:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.8:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.8:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.3.9:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.3.9:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:concretecms:concrete_cms:9.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:concretecms:concrete_cms:9.5.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-18110: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-96289 – Uncontrolled Recursion vulnerability in Apache Thrift PHP bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended to...
  • CVE-2026-96287 – Inefficient Algorithmic Complexity vulnerability in Apache Thrift Perl bindings. This issue affects Apache Thrift: before 0.25.0. Users are r...
  • CVE-2026-96286 – Uncaught exception vulnerability in Apache Thrift Perl bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended to up...
  • CVE-2026-96277 – Uncaught exception, Improper Handling of Exceptional Conditions vulnerability in Apache Thrift Ruby bindings. This issue affects Apache Thrift: ...
  • CVE-2026-94658 – Inefficient Algorithmic Complexity vulnerability in Apache Thrift Lua bindings. This issue affects Apache Thrift: before 0.25.0. Users are re...