Back to CVE records
High 7.3Published May 21, 2026

CVE-2026-8197Concrete CMS 9.5.0 and below is vulnerable to Stored XSS via OAuth integration name

Updated under an hour ago ()

Does this affect you?

It affects Concrete CMS and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
7.3 HIGH (v4.0, CNA)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
Weakness (CWE)
CWE-79
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
ConcreteCMS
NVD analysis
Analyzed
Record last updated
May 22, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Concrete CMS Concrete CMS
concrete_cms:concrete_cms (from the name)
from 5.0 through 9.5.0
CNA record
concretecms concrete_cms
concretecms:concrete_cms
through 9.5.0
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.