dbcve.org
Concrete CmsApplication · Concretecms

CVE-2022-43687

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-14
Fix available
A fix is available. Upgrade to 8.5.10 or later.
See remediation →
61/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
Concrete CMS (formerly concrete5) below 8.5.10 and between 9.0.0 and 9.1.2 does not issue a new session ID upon successful OAuth authentication. Remediate by updating to Concrete CMS 9.1.3+ or 8.5.10+.

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

Concrete CMS fails to regenerate session IDs after successful OAuth authentication, creating a session fixation vulnerability where an attacker who obtains a user's session ID could hijack the session after the legitimate user completes OAuth login.

MitigationUpgrade Concrete CMS to version 9.1.3 or later, or 8.5.10 or later, to receive the session ID regeneration fix.

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.10>= 9.0.0, <= 9.1.2

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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. Determine Concrete CMS version
    Log into the dashboard and navigate to Dashboard > System & Settings > Basics > Site Name, or check the CHANGELOG.md file in the web root. The version number is displayed at the bottom-left of the dashboard interface.
    Affected if The installed version is less than 8.5.10, OR between 9.0.0 and 9.1.2 inclusive.
  2. Verify OAuth authentication is enabled
    Navigate to Dashboard > System & Settings > Authentication > Authentication Methods. Check if any OAuth provider (such as Google, Facebook, or custom OAuth) is enabled and configured.
    Affected if OAuth authentication methods are enabled and configured in the Concrete CMS installation.
  3. Check session configuration for PHP
    Inspect the PHP configuration file (php.ini) or check session settings via a PHP info page. Look for session.cookie_httponly, session.use_only_cookies, and session.regenerate_id settings.
    Affected if Session settings allow session IDs to be passed via URL (session.use_trans_sid enabled) or if session ID regeneration is disabled.
  4. Inspect session handling code (optional)
    If codebase access is available, examine the OAuth authentication controller files (typically in concrete/src/Authentication/Type/) for session ID regeneration calls after successful authentication.
    Affected if The OAuth authentication handlers do not call session_regenerate_id() or similar functions after successful login.

You are affected if your Concrete CMS version falls within < 8.5.10 or 9.0.0 to 9.1.2 AND you have OAuth authentication enabled, allowing session fixation attacks.

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.10 or later
Fixed in 8.5.10
Interim mitigation

Upgrade Concrete CMS to version 9.1.3 or later, or 8.5.10 or later, to receive the session ID regeneration fix.

Recommended fix High confidence

Concrete CMS 9.1.3+ or 8.5.10+

  1. Create a complete backup of your database and all site files
  2. Download Concrete CMS version 9.1.3 or 8.5.10 (whichever matches your major version) from the official Concrete CMS website
  3. Replace the core Concrete CMS files with the new version files, preserving your site-specific configuration
  4. Run the database upgrade process by accessing your site (Concrete CMS typically prompts for this automatically)
  5. Clear all application caches after the upgrade completes
  6. Verify that OAuth authentication works correctly and a new session ID is generated after successful login
  7. Test that your site's core functionality remains intact after the upgrade
Caveat Review Concrete CMS release notes for any breaking changes between your current version and the 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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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