Description
Concrete CMS Area API's block-create endpoint in versions 9.2.0 to 9.5.2 did not invoke the block type controller's validate() method on submitted data, which, for file-referencing blocks such as hero_image and gallery, is where the referenced file is authorized against the user's file-manager visibility. As a result, an authenticated user holding the block-add scope could store, and cause the page to render, a reference to a file that the file-manager authorization policy would otherwise reject, disclosing that file's URL and preview to the editor and to visitors of the affected page. Under public file storage, the URL and thumbnail are exposed directly; under private storage, the disclosure is limited by the permission-checked download URL. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.
Published: 2026-09-11
Score: 5.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Information Disclosure via unauthorized file references
Action: Update CMS
AI Analysis

Impact

Concrete CMS versions 9.2.0 through 9.5.2 contain a missing authorization check in the Area REST API block‑create endpoint. When a block that references files—such as hero_image or gallery—is created, the block type controller’s validate() method, which normally verifies that the user is permitted to reference the selected file, is not invoked. This omission allows an authenticated user with block‑add scope to store and cause a page to render a reference to a file that the file‑manager visibility policy would otherwise reject, thereby disclosing the file’s URL and preview. The weakness corresponds to CWE‑862: Missing Authorization.

Affected Systems

Concrete CMS, versions 9.2.0 through 9.5.2

Risk and Exploitability

The vulnerability has a CVSS v4.0 score of 5.1, indicating moderate severity. The EPSS score is less than 1 percent, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector requires an authenticated user who possesses block‑add scope, the attacker can obtain the file URL and preview, exposing files the user otherwise could not access.

Generated by OpenCVE AI on September 15, 2026 at 20:07 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Check Concrete CMS release notes or vendor documentation for any the Area REST API block‑create path.
  • If an upgrade cannot be performed immediately, revoke the block‑add scope from users who lack file‑manager permissions and restrict this ability to trusted administrators.
  • Consider disabling or removing file‑referencing block types that are not essential to reduce the attack surface.

Generated by OpenCVE AI on September 15, 2026 at 20:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 24 Sep 2026 20:15:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:concretecms:concrete_cms:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


Mon, 14 Sep 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 12 Sep 2026 22:00:00 +0000

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

Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
Description Concrete CMS Area API's block-create endpoint in versions 9.2.0 to 9.5.2 did not invoke the block type controller's validate() method on submitted data, which, for file-referencing blocks such as hero_image and gallery, is where the referenced file is authorized against the user's file-manager visibility. As a result, an authenticated user holding the block-add scope could store, and cause the page to render, a reference to a file that the file-manager authorization policy would otherwise reject, disclosing that file's URL and preview to the editor and to visitors of the affected page. Under public file storage, the URL and thumbnail are exposed directly; under private storage, the disclosure is limited by the permission-checked download URL. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.
Title Concrete CMS 9.2.0 to 9.5.2 is vulnerable to Missing authorization in the Concrete CMS Area REST API block-create path letting an editor reference files outside their file-manager permissions
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 5.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N'}


Subscriptions

Concretecms Concrete Cms
cve-icon MITRE

Status: PUBLISHED

Assigner: ConcreteCMS

Published:

Updated: 2026-09-14T13:00:31.887Z

Reserved: 2026-07-30T18:04:50.763Z

Link: CVE-2026-68535

cve-icon Vulnrichment

Updated: 2026-09-14T12:57:41.938Z

cve-icon NVD

Status : Analyzed

Published: 2026-09-11T21:17:13.443

Modified: 2026-09-24T20:05:45.390

Link: CVE-2026-68535

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-15T20:15:14Z

Weaknesses