dbcve.org
Concrete CmsApplication · Concretecms

CVE-2022-30120

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-24
Fix available
A fix is available. Upgrade to 8.5.8 / 9.1.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
XSS in /dashboard/blocks/stacks/view_details/ - old browsers only. When using an older browser with built-in XSS protection disabled, insufficient sanitation where built urls are outputted can be exploited for Concrete 8.5.7 and below as well as Concrete 9.0 through 9.0.2 to allow XSS. This cannot be exploited in modern-day web browsers due to an automatic input escape mechanism. Concrete CMS Security team ranked this vulnerability 3.1with CVSS v3.1 Vector AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N. Sanitation has been added where built urls are output. Credit to Credit to Bogdan Tiron from FORTBRIDGE (https://www.fortbridge.co.uk/ ) for reporting

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site scripting vulnerability in Concrete CMS (versions 8.5.7 and below, and 9.0-9.0.2) in the /dashboard/blocks/stacks/view_details/ endpoint. Insufficient sanitization of built URLs allows XSS injection when viewed in older browsers that lack automatic XSS protection mechanisms.

MitigationUpdate Concrete CMS to the latest version which includes proper URL output sanitization. Alternatively, restrict access to the affected dashboard area to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Concrete CmsApplication
Affected:< 8.5.8>= 9.0.0, < 9.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Concrete CMS version
    Locate the version file or check the dashboard footer for the version number. Common locations include the login page footer, dashboard footer, or a version.php file in the application directory.
    Affected if The version is 8.5.7 or below, or falls between 9.0.0 and 9.0.2 inclusive.
  2. Verify access to the affected dashboard endpoint
    Attempt to access or check the URL /dashboard/blocks/stacks/view_details/ in the browser while logged into the admin dashboard. Determine if this route is reachable.
    Affected if The dashboard area is accessible to any user account in the system.
  3. Confirm Stacks feature is in use
    Navigate to the Stacks section in the dashboard (Dashboard > Blocks > Stacks) and check if any stack pages or records exist in the database.
    Affected if The Stacks feature is enabled and contains data, making the view_details endpoint functional.
  4. Check browser XSS protection status
    Identify if the browsers used to access the admin dashboard are older browsers without built-in XSS protection (such as older Internet Explorer versions).
    Affected if Older browsers without automatic XSS filtering are used to access the affected endpoint.

A user is affected if their Concrete CMS installation version is 8.5.7 or below, or between 9.0.0 and 9.1.0, AND they have access to the dashboard stacks view_details area while using browsers without XSS protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.5.8 / 9.1.0 or later
Fixed in 8.5.89.1.0
Interim mitigation

Update Concrete CMS to the latest version which includes proper URL output sanitization. Alternatively, restrict access to the affected dashboard area to trusted users only.

Recommended fix High confidence

Concrete CMS 8.5.8 (for 8.x) or Concrete CMS 9.1.0 (for 9.x)

  1. Backup the existing database and files before proceeding with the upgrade
  2. Download the fixed version: Concrete CMS 8.5.8 or later for 8.x branches, or Concrete CMS 9.1.0 or later for 9.x branches from the official Concrete CMS website
  3. Extract the new version files and replace the existing installation files on the server
  4. Run any available database migrations or update scripts included in the new version
  5. Verify the installation by logging into the dashboard and navigating to /dashboard/blocks/stacks/view_details/ to confirm the fix is applied
  6. Test that stacks and block functionality works correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Concrete Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30120 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30120 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data