Description
Concrete CMS below 9.5.3 was vulnerable to Cross-Site Request Forgery in the dashboard SEO Excluded Words page. The reset() controller action cleared the administrator-configured reserved-word list (concrete.seo.exclude_words) but did not validate the anti-CSRF token that the reset modal emitted, and it did not restrict the request to the POST method. A remote attacker who lured an authenticated user with SEO access to a crafted page could revert the reserved-word list to its default and silently alter future URL-slug generation for pages, files, topics, and other objects created through the Text urlify service, undoing the site's configured SEO slug policy. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.
Published: 2026-09-15
Score: 2.3 Low
EPSS: < 1% Very Low
KEV: No
Impact: Unintended configuration change via CSRF enabling an attacker to restore the default reserved‑word list and alter URL slug rules
Action: Update CMS
AI Analysis

Impact

Concrete CMS versions below 9.5.3 have a CSRF vulnerability in the Dashboard SEO Excluded Words Reset endpoint. The reset action clears the administrator‑configured reserved‑word list without validating the CSRF token or restricting the request to the POST method. An attacker can lure an authenticated user with SEO privileges to a crafted page, causing the site to revert its reserved‑word list to default values and silently change how slugs are generated for pages, files and other objects. This undermines the site’s configured SEO slug policy and can break URLs and damage search engine rankings.

Affected Systems

All installations of Concrete CMS running a version earlier than 9.5.3 are affected. The vulnerability occurs on the Concrete CMS dashboard under the SEO management area.

Risk and Exploitability

The CVSS v4.0 score of 2.3 indicates low severity; the EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a web‑based CSRF attack that requires an attacker to trick a legitimate authenticated user to trigger the reset. Because the attack requires an authenticated session with SEO access, the risk to an unauthenticated attacker is low, but any impacted site’s SEO and URL scheme integrity could be compromised.

Generated by OpenCVE AI on September 16, 2026 at 01:07 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Concrete CMS to version 9.5.3 or later
  • If an upgrade cannot be performed immediately, restrict access to the SEO dashboard to a minimal set of trusted administrators and disable the reset functionality
  • Deploy a Web Application Firewall rule to block requests to the reset endpoint that lack a valid CSRF token or are not POST, preventing the CSRF exploit.

Generated by OpenCVE AI on September 16, 2026 at 01:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 15 Sep 2026 22:30:00 +0000

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

Tue, 15 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Tue, 15 Sep 2026 19:00:00 +0000

Type Values Removed Values Added
Description Concrete CMS below 9.5.3 was vulnerable to Cross-Site Request Forgery in the dashboard SEO Excluded Words page. The reset() controller action cleared the administrator-configured reserved-word list (concrete.seo.exclude_words) but did not validate the anti-CSRF token that the reset modal emitted, and it did not restrict the request to the POST method. A remote attacker who lured an authenticated user with SEO access to a crafted page could revert the reserved-word list to its default and silently alter future URL-slug generation for pages, files, topics, and other objects created through the Text urlify service, undoing the site's configured SEO slug policy. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.
Title Concrete CMS below 9.5.3 is vulnerable to Cross-Site Request Forgery (CSRF) in Dashboard SEO Excluded Words Reset Endpoint
Weaknesses CWE-352
References
Metrics cvssV4_0

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


Subscriptions

Concretecms Concrete Cms
cve-icon MITRE

Status: PUBLISHED

Assigner: ConcreteCMS

Published:

Updated: 2026-09-15T19:40:58.435Z

Reserved: 2026-08-27T18:23:01.366Z

Link: CVE-2026-81920

cve-icon Vulnrichment

Updated: 2026-09-15T19:40:53.763Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-15T19:17:41.350

Modified: 2026-09-16T19:16:15.097

Link: CVE-2026-81920

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-16T01:15:17Z

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)