2000 matches found
CVE-2026-93659
Concrete CMS Community Store before 2.7.8 renders customer-supplied order fields without HTML escaping in checkout and admin views. Unauthenticated attackers can store script payloads in billing name, email, or phone fields that execute in authenticated manager sessions to create rogue accounts o...
CVE-2026-93659
Concrete CMS Community Store before version 2.7.8 is vulnerable to a stored cross-site scripting (XSS) flaw. Customer-supplied order fields—specifically billing name, email, and phone —are rendered without HTML escaping in both the checkout and admin views (see order_slip.php). An unauthenticated...
EUVD-2026-82941
Concrete CMS Community Store before 2.7.8 renders customer-supplied order fields without HTML escaping in checkout and admin views. Unauthenticated attackers can store script payloads in billing name, email, or phone fields that execute in authenticated manager sessions to create rogue accounts o...
CVE-2026-8239
CVE-2026-8239 CVE-2026-8239 es una vulnerabilidad de Referencia Directa a Objetos Insegura IDOR que afecta a Concrete CMS 9.5.0 y anteriores.La vulnerabilidad existe en el endpoint /ccm/frontend/conversations/getrating, que permite a un atacante determinar si existe un mensaje de conversación y...
CVE-2026-8337
CVE-2026-8337 CVE-2026-8337 es una vulnerabilidad de Referencia Directa a Objetos Insegura IDOR en Concrete CMS que afecta a la función de Encuestas. A diferencia de CVE-2026-8347 que involucraba asociaciones de Express, esta vulnerabilidad permite que un atacante no autenticado participe en una...
CVE-2026-8237
CVE-2026-8237 CVE-2026-8237 es una vulnerabilidad de Referencia Directa Insegura a Objetos IDOR causada por la falta de comprobaciones de autorización en Concrete CMS 9.5.0 y anteriores. La falla existe en el endpoint /ccm/frontend/conversations/messagedetail, que devuelve el contenido completo d...
Concrete CMS <9.5.1 - Unauthenticated File-Usage Internal Metadata Disclosure
Concrete CMS 9.5.0 and below is vulnerable to IDOR combined with a missing authentication gate. The endpoint /ccm/system/dialogs/file/usage/fID accepts an integer file ID in the URL and returns internal site structure data page IDs, versions, URL paths to anyone who sends a GET request. id:...
Concrete CMS <= 9.5.0 - Unauthenticated Conversation Message Disclosure (IDOR)
Concrete CMS = 9.5.0 contains an IDOR caused by insufficient access control in /ccm/frontend/conversations/messagedetail endpoint, letting unauthenticated attackers enumerate conversation messages and attachments. id: CVE-2026-8237 info: name: Concrete CMS = 9.5.0 - Unauthenticated Conversation...
Concrete CMS <9.5.1 - Unauthenticated File Usage Disclosure
Concrete CMS 9.5.0 and below is vulnerable to unauthenticated file usage disclosure via missing permission check in the usage controller. id: CVE-2026-6826 info: name: Concrete CMS 9.5.1 - Unauthenticated File Usage Disclosure author: str4k3r severity: medium description: | Concrete CMS 9.5.0 and...
CVE-2026-85387
Concrete CMS before 9.5.4 re-authorized OAuth REST API requests from the bearer token alone and did not re-check the state of the account the token had been issued to. The resource server's authorization validator confirmed only that a token existed, had not expired, and had not been explicitly...
CVE-2026-18120
Concrete CMS before 9.5.3 exposed a legacy Express entry search endpoint that returned entry result JSON without invoking the canViewExpressEntries permission check applied by the normal dashboard and CSV Export flow. An unauthenticated visitor who knew or discovered an Express entity identifier...
CVE-2026-87031
n Concrete CMS 9.2.0 through 9.5.3, the REST API user creation endpoint POST /ccm/api/1.0/users, the add method of concrete/src/Api/Controller/Users.php did not perform a permission check before creating an account. As a result, any valid OAuth token carrying the users:add scope, including a...
CVE-2026-87028
Concrete CMS 9 through 9.5.3 did not confirm that a board InstanceItem submitted to the custom-slot preview endpoint belonged to the board instance the requesting user was authorized to edit, and did not enforce page-view permission before generating page-backed summary content. As a result, an...
CVE-2026-85385
Concrete CMS below 9.5.4 did not validate the user timezone value uTimezone on write and rendered it without output encoding on the Dashboard user management page, where Date::getTimezoneDisplayName returns any non-IANA value unchanged. A stored cross-site scripting payload saved in this field...
CVE-2026-85386
Concrete CMS before 9.5.4 did not sanitize XML and XSLT documents uploaded through a public Form Block file-upload question. Plain XML uploads were validated by file extension only and stored as publicly accessible files that were served inline from the application's own origin. An unauthenticate...
CVE-2026-18120
Concrete CMS before 9.5.3 exposed a legacy Express entry search endpoint that returned entry result JSON without invoking the canViewExpressEntries() permission check applied by the normal dashboard and CSV Export flow. An unauthenticated visitor who knew or discovered an Express entity identifie...
EUVD-2026-80894
Concrete CMS before 9.5.3 exposed a legacy Express entry search endpoint that returned entry result JSON without invoking the canViewExpressEntries permission check applied by the normal dashboard and CSV Export flow. An unauthenticated visitor who knew or discovered an Express entity identifier...
CVE-2026-18120 Missing Authorization in legacy Express entries search endpoint allows disclosure of Express entry data
Concrete CMS before 9.5.3 exposed a legacy Express entry search endpoint that returned entry result JSON without invoking the canViewExpressEntries permission check applied by the normal dashboard and CSV Export flow. An unauthenticated visitor who knew or discovered an Express entity identifier...
CVE-2026-85387 Concrete CMS before 9.5.4 allows a deactivated user to retain OAuth-authenticated REST API access
Concrete CMS before 9.5.4 re-authorized OAuth REST API requests from the bearer token alone and did not re-check the state of the account the token had been issued to. The resource server's authorization validator confirmed only that a token existed, had not expired, and had not been explicitly...
CVE-2026-85387
Concrete CMS before 9.5.4 failed to re-check account state when validating OAuth bearer tokens for its REST API. The authorization validator confirmed only that a token existed, had not expired, and had not been explicitly revoked — so deactivated , deleted , or locked (pending forced password re...