Technical impact
OpenCTI is a platform for managing cyber threat intelligence. The GraphQL endpoint allowed query operations to be sent via HTTP GET requests because CSRF prevention was disabled, which places the full GraphQL query and arguments in the request URL. This behaviour caused server and reverse‑proxy logs, browser history, and shared caches to retain sensitive filter values, marking‑restricted identifiers and investigation search arguments, enabling anyone with access to these records to recover a legitimate user’s query contents. GraphQL mutations were not accepted over GET, and the flaw does not provide code execution, but it can lead to unintended disclosure of confidential query data. The vulnerability is present in any OpenCTI deployment that uses a version prior to 7.260722.0. The affected product is the OpenCTI‑Platform opencti, and all releases before that version may be impacted. With a CVSS score of 6.3, the risk is moderate. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog. Exploitation can occur by simply sending a GET request containing a GraphQL query; the attacker can then obtain the query string from logs, browser history, or cached responses. Because the attack surface is public and the flaw relies on logging and caching mechanisms, the likelihood is medium if the environment is not otherwise hardened.
Affected Systems
OpenCTI‑Platform opencti versions prior to 7.260722.0 are affected.
Risk and Exploitability
The CVSS score of 6.3 indicates a medium severity. The EPSS score is not provided, and the vulnerability is not listed in the CISA KEV catalog. An attacker can exploit this flaw simply by sending a GET request with a GraphQL query; the query is stored in logs, browser history, and shared caches, allowing the attacker to retrieve sensitive query data. There is no code execution path or privilege escalation. Hence, the risk is moderate when logs or caches are accessible to potential adversaries.