CVE-2026-8197: Concrete CMS 9.5.0 and below is vulnerable to Stored XSS via OAuth integration name
Concrete CMS 9.5.0 and below is vulnerable to Stored XSS via OAuth integration name. The OAuth authorize template renders the integration name (admin-controlled) through Concrete's t() translation helper as a sprintf-style format. The <strong>...</strong> wrap is built by PHP string interpolation before t() runs, so the integration name lands in the translated output as raw HTML. A rogue admin could potentially snoop on login submissions.The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 7.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Thanks Yonatan Drori (Tenzai) for reporting.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-8197?
The severity of CVE-2026-8197 is high with a CVSS score of 7.3.
How do I fix CVE-2026-8197?
To fix CVE-2026-8197, upgrade to Concrete CMS version 9.5.1 or later.
What kind of vulnerability is CVE-2026-8197?
CVE-2026-8197 is a Stored Cross-Site Scripting (XSS) vulnerability.
What causes the vulnerability in CVE-2026-8197?
The vulnerability in CVE-2026-8197 is caused by improper handling of the OAuth integration name during rendering.
Who is affected by CVE-2026-8197?
All users of Concrete CMS version 9.5.0 and below are affected by CVE-2026-8197.