Description
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.
Published: 2026-05-21
Score: 7.3 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Concrete CMS versions 9.5.0 and earlier contain a stored cross‑site scripting flaw in the OAuth integration mechanism. The integration name field, controllable by administrators, is inserted into the OAuth authorization page using PHP string interpolation and passed to the translation helper t() as raw, unescaped sprintf format. As a result, an attacker who can create or modify an integration name can inject arbitrary HTML or JavaScript into the page. If the victim visits the affected page, the injected script runs in the context of the site, permitting session hijacking, data exfiltration, or defacement. The flaw could also allow an administrator to snoop on login submissions, compromising the confidentiality of authentication credentials. The vulnerability affects Concrete CMS releases 9.5.0 and earlier. Administrators running those versions should review any OAuth integrations. The problem does not affect later releases such as 9.5.1 or 9.5.2, which contain the fix. The CVSS v4.0 score is 7.3, classifying the vulnerability as high severity. Because the issue requires an account with administrative privileges to supply a malicious integration name, the practical attack surface is limited to legitimate administrators or compromised admin credentials. No public exploit has been identified, and the EPSS score is unavailable, but the stored XSS nature means that once an admin injects a payload, any user who accesses the page will be affected. The vulnerability is not listed in the CISA KEV catalog, suggesting there are no known widespread exploitation campaigns, but clients should not rely on that as a safeguard. The likely attack vector is through a compromised or rogue administrator creating a malicious OAuth integration name that will be rendered to site users.

Affected Systems

Concrete CMS versions 9.5.0 and earlier are impacted. The misconfiguration involves the OAuth integration name field stored in the database. Administrators on these releases should immediately audit and, if necessary, remove or correct any custom OAuth integration names. Versions 9.5.1 and later contain the patch and are not affected. The affected product is the content management system provided by Concrete CMS. The flaw does not affect other products or versions released after 9.5.0.

Risk and Exploitability

The CVSS v4.0 score of 7.3 classifies the flaw as high severity. The vulnerability requires an account with administrative privileges to inject a malicious payload; therefore, the practical attack surface is confined to legitimate administrators or attackers who have compromised such accounts. No public exploit has been documented, and the EPSS score is not available, but the stored XSS characteristic means that once the payload is stored, every user who visits the OAuth authorization page will be impacted. The vulnerability is not catalogued in the CISA KEV list, indicating no known widespread exploitation campaigns, but this does not mitigate the need for remediation.

Generated by OpenCVE AI on May 21, 2026 at 22:36 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Concrete CMS 9.5.1 or newer.
  • Remove or disable OAuth integrations with untrusted names; ensure all integration names contain only safe characters.
  • Apply a Content Security Policy that blocks inline scripts to mitigate any remaining XSS risk.

Generated by OpenCVE AI on May 21, 2026 at 22:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 21 May 2026 23:00:00 +0000

Type Values Removed Values Added
First Time appeared Concretecms
Concretecms concrete Cms
Vendors & Products Concretecms
Concretecms concrete Cms

Thu, 21 May 2026 21:00:00 +0000

Type Values Removed Values Added
Description 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.
Title Concrete CMS 9.5.0 and below is vulnerable to Stored XSS via OAuth integration name
Weaknesses CWE-79
References
Metrics cvssV4_0

{'score': 7.3, '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'}


Subscriptions

Concretecms Concrete Cms
cve-icon MITRE

Status: PUBLISHED

Assigner: ConcreteCMS

Published:

Updated: 2026-05-21T20:29:58.830Z

Reserved: 2026-05-08T23:37:43.165Z

Link: CVE-2026-8197

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-21T21:16:33.240

Modified: 2026-05-21T21:16:33.240

Link: CVE-2026-8197

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-21T22:45:21Z

Weaknesses