dbcve.org
Concrete CmsApplication · Concretecms

CVE-2022-30118

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
Title for CVE: XSS in /dashboard/system/express/entities/forms/save_control/[GUID]: old browsers only.Description: When using Internet Explorer with the XSS protection disabled, editing a form control in an express entities form for Concrete 8.5.7 and below as well as Concrete 9.0 through 9.0.2 can 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 2 with CVSS v3.1 Vector AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N. Thanks zeroinside 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

A stored Cross-Site Scripting (XSS) vulnerability exists in Concrete CMS express entities form control functionality at /dashboard/system/express/entities/forms/save_control/[GUID]. The vulnerability can only be exploited when using Internet Explorer with XSS protection disabled; modern browsers automatically escape inputs and prevent exploitation.

MitigationUpgrade Concrete CMS to version 8.5.8 or later, or 9.0.3 or later. As a compensating control, ensure XSS protection is enabled in Internet Explorer if continued use is required.

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
    Access /dashboard/system information or check version.php file in the installation directory to read the CMS_VERSION constant or $CMS_VERSION variable
    Affected if The version is less than 8.5.8 OR >= 9.0.0 but less than 9.1.0
  2. Confirm Express entities feature is in use
    Navigate to /dashboard/system/express/entities or check database for entries in the Express entity tables
    Affected if Express entities have been created or configured in the CMS
  3. Check for saved form controls in Express entities
    Review the express_form_controls database table or access /dashboard/system/express/entities/forms to view saved controls
    Affected if Any custom form controls have been saved in Express entity forms
  4. Review access logs for the vulnerable endpoint
    Search web server access logs for requests to /dashboard/system/express/entities/forms/save_control/ followed by a GUID pattern
    Affected if Requests to the save_control endpoint with GUIDs are found in logs

Your environment is affected if the installed Concrete CMS version falls within < 8.5.8 or >= 9.0.0 to < 9.1.0 AND Express entities with custom form controls have been configured.

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

Upgrade Concrete CMS to version 8.5.8 or later, or 9.0.3 or later. As a compensating control, ensure XSS protection is enabled in Internet Explorer if continued use is required.

Recommended fix High confidence

Upgrade to Concrete CMS 8.5.8 or 9.1.0 (or later)

  1. Backup your Concrete CMS database and files before upgrading
  2. Review the Concrete CMS upgrade documentation for your current version
  3. Download Concrete CMS 8.5.8 (for 8.x installations) or 9.1.0+ (for 9.x installations) from the official concretecms.org website
  4. Follow the standard upgrade process: upload new files, run /ccm/system/upgrade or use the dashboard updater
  5. Verify the upgrade was successful by logging into the dashboard and checking the version number
  6. Clear any caching systems (application cache, opcode cache, CDN) after upgrade
Caveat Review Concrete CMS release notes for any configuration or theme changes between your current version and target version before upgrading

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30118 — 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-30118 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