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

Concrete CMS below version 9.4.8 is vulnerable to a stored cross-site scripting (XSS) in the "Legacy Form" block.

CVE-2026-3241

Description

In Concrete CMS below version 9.4.8, a stored cross-site scripting (XSS) vulnerability exists in the "Legacy Form" block. An authenticated user with permissions to create or edit forms (e.g., a rogue administrator) can inject a persistent JavaScript payload into the options of a multiple-choice question (Checkbox List, Radio Buttons, or Select Box). This payload is then executed in the browser of any user who views the page containing the form. 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 M3dium for reporting.

AI Insight

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

Stored XSS in Concrete CMS Legacy Form block allows authenticated administrators to inject persistent JavaScript into multiple-choice question options.

Vulnerability

Description

CVE-2026-3241 is a stored cross-site scripting (XSS) vulnerability in the Legacy Form block of Concrete CMS versions prior to 9.4.8 [1]. The flaw exists in the options of multiple-choice question types—Checkbox List, Radio Buttons, and Select Box—where user-supplied input is not properly sanitized before being stored. An authenticated user with permissions to create or edit forms can inject a persistent JavaScript payload into these fields [1][2].

Exploitation

Exploitation requires an account with administrative privileges or equivalent permissions to manage forms [2]. The attacker crafts a malicious JavaScript payload and inserts it into the form’s multiple-choice options. When any user, including non-administrators, visits a page that displays the compromised form, the payload executes in their browser [1]. The attack vector is network-based with low complexity, but requires high privileges and user interaction to trigger [1].

Impact

Successful exploitation leads to arbitrary JavaScript execution in the context of the victim’s session. This can result in data theft, session hijacking, or defacement. The CVSS v4.0 score is 4.8 (medium severity) with a vector string indicating no confidentiality impact but a low integrity impact [1]. The vulnerability does not affect the availability of the system [1].

Mitigation

The issue is fixed in Concrete CMS version 9.4.8 [2]. The fix was implemented in commit 12826, which sanitizes the options input of the Legacy Form block [3]. Users should upgrade to 9.4.8 or later immediately. No workarounds are documented; upgrading is the recommended course of action.

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

1
  • Concrete CMS/Concrete CMSv5
    Range: 5

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.