CVE-2022-43556
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 · uneditedConcrete CMS (formerly concrete5) below 8.5.10 and between 9.0.0 and 9.1.2 is vulnerable to XSS in the text input field since the result dashboard page output is not sanitized. The Concrete CMS security team has ranked this 4.2 with CVSS v3.1 vector AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N Thanks @_akbar_jafarli_ for reporting. Remediate by updating to Concrete CMS 8.5.10 and Concrete CMS 9.1.3.
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 confidenceConcrete CMS versions below 8.5.10 and 9.0.0-9.1.2 are vulnerable to stored XSS in the dashboard's result page where user text input is not sanitized before output, allowing injection of malicious scripts.
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< 8.5.10>= 9.0.0, <= 9.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Concrete CMS installed versionLocate the version file or check the dashboard footer for the version number. Common locations: /concrete/config.php or login to admin dashboard and check footer for version string.Affected if Version is below 8.5.10 or between 9.0.0 and 9.1.2 inclusive
-
Confirm dashboard access is enabledVerify that the Concrete CMS dashboard is accessible. Log in as an administrator and navigate to the dashboard area. The vulnerability exists in the dashboard result page where user input is displayed.Affected if Dashboard functionality is active and users can access it
-
Identify if dashboard form input is usedCheck if the dashboard includes any result pages or forms that accept user text input and display it back. The XSS flaw occurs when user-supplied text is rendered without sanitization in dashboard output areas.Affected if Dashboard contains input fields that accept and display user text without sanitization
You are affected if your Concrete CMS installation runs version 8.5.10 or below, or version 9.0.0 through 9.1.2, and the dashboard with user input functionality is accessible and in use.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.5.10
Update Concrete CMS to version 8.5.10 or 9.1.3 to apply the security patch that properly sanitizes user input in the dashboard.
Concrete CMS 8.5.10 (for 8.x branch) or Concrete CMS 9.1.3 (for 9.x branch)
- Backup the Concrete CMS database and files before proceeding with any upgrade
- Determine the current version of your Concrete CMS installation (8.x branch or 9.x branch)
- For installations on 8.x branch (versions < 8.5.10): Download Concrete CMS 8.5.10 from the official Concrete CMS website
- For installations on 9.x branch (versions 9.0.0 - 9.1.2): Download Concrete CMS 9.1.3 from the official Concrete CMS website
- Follow the official Concrete CMS upgrade documentation to apply the update
- Verify the installation was successful by logging into the dashboard
- Test that the text input field vulnerability has been remediated by attempting to submit and render content
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43556 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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