VYPR
Moderate severityNVD Advisory· Published Mar 4, 2026· Updated Mar 4, 2026

Concrete CMS below 9.4.8 is vulnerable to Stored XSS via Legacy form

CVE-2026-3240

Description

In Concrete CMS below version 9.4.8, a user with permission to edit a page with element Legacy form can perform a stored XSS attack towards high-privilege accounts via the Question field. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 4.8 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Thanks minhnn42, namdi and quanlna2 from VCSLab-Viettel Cyber Security for reporting.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A stored XSS vulnerability in Concrete CMS's Legacy Form block allows users with page edit permissions to inject malicious scripts via the Question field, targeting high-privilege accounts.

Vulnerability

Overview

CVE-2026-3240 is a stored cross-site scripting (XSS) vulnerability found in Concrete CMS versions prior to 9.4.8. The flaw resides in the Legacy Form block, specifically within the Question field. A user who has permission to edit a page containing this block can inject arbitrary JavaScript or HTML into the Question field, which is then stored and later rendered without proper sanitization [1][2].

Exploitation

Prerequisites

To exploit this vulnerability, an attacker must have a Concrete CMS account with at least page editing privileges and access to a page that uses the Legacy Form block. The attack is performed by submitting a crafted payload in the Question field. When a high-privilege user (such as an administrator) views the affected page, the stored script executes in their browser session. The CVSS v4.0 score is 4.8, with a vector of AV:N/AC:L/AC:L/AT:N/PR:H/UI:P, indicating that while the attacker requires high privileges, the attack complexity is low and no special attack prerequisites are needed beyond network access [1].

Impact

Successful exploitation allows the attacker to execute arbitrary JavaScript in the context of the victim's session. This can lead to actions such as stealing session cookies, performing administrative actions on behalf of the victim, or defacing the page. The impact is limited to integrity (VI:L) and does not affect confidentiality or availability directly, but the stored XSS can be used as a stepping stone for further attacks [1].

Mitigation

The vulnerability is fixed in Concrete CMS version 9 only and is fixed in version 9.4.8. Users should upgrade to this version or later to remediate the issue. No workarounds are mentioned in the advisory. The issue was reported by researchers from VCSLab-Viettel Cyber Security [1][2].

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
concrete5/concrete5Packagist
< 9.4.89.4.8

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

4

News mentions

0

No linked articles in our index yet.