Vulnerability in Concrete CMS (CVE-2026-18115)
Summary
Vulnerability in Concrete CMS (CVE-2026-18115). Risk of unauthorized operations or information disclosure. Exploitable via PUT /ccm/api/1.0/users/{uID}.
Original description
The description as published by the source.
Concrete CMS 9.2.0 to 9.5.2 did not enforce per-field edit_user_properties permissions on the REST API user write endpoints (PUT /ccm/api/1.0/users/{uID} and POST /ccm/api/1.0/users/{uID}/change_password). A user with an update-scoped OAuth token and permission to edit only one non-sensitive field could change another non-superuser's password, username, email, and attributes, taking over that account. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 7.4 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-18115 has been found in Concrete CMS.
Attackers can target a specific entry point like PUT /ccm/api/1.0/users/{uID} over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Concrete CMS CVE-2026-18115" on the vendor's site.
CVE-2026-18115 (Concrete CMS) — CWE-862
Attack surface: PUT /ccm/api/1.0/users/{uID} / POST /ccm/api/1.0/users/{uID}/change_password
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in Concrete CMS. Attackers reach the vulnerable code path via PUT /ccm/api/1.0/users/{uID}.
Check the vendor advisory for the affected versions of Concrete CMS. Attack surface: PUT /ccm/api/1.0/users/{uID} / POST /ccm/api/1.0/users/{uID}/change_password.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /ccm/api/1.0/users/{uID} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Concrete CMS を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'PUT /ccm/api/1.0/users/{uID}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /ccm/api/1.0/users/{uID}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /ccm/api/1.0/users/{uID} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web documentation.concretecms.org
- web nvd.nist.gov
- web github.com