/

CVE-2026-93659

Severity:

HIGH RISK

(8.1)

Stored XSS (CWE-79) in Concrete CMS Checkout Views

CVE-2026-93659

Awaiting Analysis

Vulnerability type

Category:

Stored Cross-Site Scripting

CWE:

CWE-79

Impact:

Authenticated session compromise, unauthorized account creation, and data exfiltration

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Concrete CMS Community Store contains a stored cross-site scripting vulnerability because customer-supplied order fields may be rendered without HTML escaping in checkout and administrative views. An unauthenticated attacker could store a script in billing details that executes when an authenticated manager views the affected data, potentially enabling account creation or sensitive data theft.

Affected context

The issue can occur in Community Store deployments that accept customer values such as billing names, email addresses, or phone numbers and later display those values in checkout or administrative manager views without context-appropriate output encoding. Risk depends on whether an attacker can submit an order and whether a privileged manager subsequently views the stored order information.

Exploit preconditions

  • Attack surface: Public checkout or order-submission functionality
  • Required access: Ability to submit customer-controlled billing or contact fields; authentication may not be required
  • Trigger point: A manager or other authenticated user views the affected order in checkout or an administrative interface
  • Why exploitation is possible: Submitted data is stored and later inserted into an HTML-rendered context without adequate output encoding

Why this happens

The underlying bug is a failure to treat customer-supplied order fields as untrusted output. When stored values are inserted into HTML without context-appropriate escaping or sanitization, browser-interpreted content can execute in the security context of the user viewing the page. This behavior maps to CWE-79, Improper Neutralization of Input During Web Page Generation, commonly known as cross-site scripting.

Potential impact

  • A malicious script may execute in an authenticated manager's browser
  • An attacker could create rogue accounts or perform actions using the manager's session
  • Sensitive administrative or customer data could be exposed
  • Session-related information or page contents could be exfiltrated
  • Administrative workflows could be altered or abused

General mitigation guidance

Mitigation generally focuses on enforcing trust boundaries for all customer fields and applying context-appropriate output encoding at every rendering sink. Secure-by-default templating should escape dynamic values unless a narrowly defined, reviewed safe-content exception is required. Input validation can restrict values to expected formats, but it should complement rather than replace output encoding. Administrative interfaces should use strong authentication, least privilege, and protections that limit the actions available to compromised sessions. Content Security Policy and related browser controls can provide additional defense in depth.

How teams detect issues like this

Detection can include static analysis for unescaped template variables, direct HTML concatenation, and rendering helpers that bypass automatic escaping. Code review should examine every path from order fields to checkout and administrative views, including stored-data re-rendering. Dynamic testing can submit benign marker values containing HTML metacharacters and verify that they are encoded rather than interpreted. CI policy checks, template linting, and automated security review tools can help identify unsafe output patterns before deployment.

Sources

SourceLink
github.comgithub.com/concretecms-community-store/community_store
github.comgithub.com/concretecms-community-store/community_store/blob/v2.7.7/elements/order_slip.php
github.comgithub.com/concretecms-community-store/community_store/commit/2a802d6a5717f4e351ef21fdf8bdaf8061c40109
github.comgithub.com/concretecms-community-store/community_store/releases/tag/v2.7.8
vulncheck.comvulncheck.com/advisories/concrete-cms-community-store-before-2.7.8-stored-xss

Frequently asked

questions

It may be exploitable through a public checkout or order-submission endpoint when an attacker can submit customer-controlled values and a manager later views the affected record.

The described attack path does not require attacker authentication, although successful impact depends on an authenticated manager viewing the stored data.

Treat all order fields as untrusted and apply context-appropriate output encoding at every HTML rendering point, supported by narrowly scoped validation and sanitization.

Use escaping-by-default templates, review stored-data rendering paths, test administrative views with hostile input markers, and enforce automated checks for bypasses of output encoding.

Find out what's already
exploitable in your codebase.