dbcve.org
ConcertApplication · Ibm

CVE-2025-36018

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-17
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
72/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
IBM Concert 1.0.0 through 2.1.0 for Z hub component is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.

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 · moderate confidence

IBM Concert for Z hub component versions 1.0.0 through 2.1.0 is vulnerable to cross-site request forgery (CSRF). This allows attackers to trick authenticated users into unknowingly submitting malicious requests to the hub component, potentially executing unauthorized actions such as data modification or configuration changes.

MitigationImplement anti-CSRF protection by adding unique CSRF tokens to all state-changing requests and validating the Origin/Referer headers server-side, or enable SameSite cookie attributes.

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
ConcertApplication
Affected:>= 1.0.0, < 2.2.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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 if IBM Concert for Z hub component is installed
    Locate the IBM Concert installation directory or running process for the hub component. Check common installation paths or use process enumeration tools to find the Concert hub service.
    Affected if IBM Concert hub component is present and running in the environment
  2. Determine the installed version of IBM Concert
    Access the IBM Concert administrative interface or version information endpoint, or inspect version metadata files in the installation directory.
    Affected if The installed version falls within 1.0.0 through 2.1.0 inclusive
  3. Compare your version to the affected range
    Verify the exact version number against the affected range: versions 1.0.0 up to and including 2.1.0 are vulnerable. Versions 2.2.0 and later are not affected.
    Affected if The version is >= 1.0.0 and < 2.2.0
  4. Inspect whether anti-CSRF tokens are implemented
    Examine state-changing requests (such as form submissions or API POST/PUT/DELETE calls) to determine if unique CSRF tokens are included with each request.
    Affected if State-changing requests do not include unique CSRF tokens or do not validate Origin/Referer headers
  5. Check cookie security attributes
    Inspect the session cookies Set-Cookie headers to see if SameSite attribute is set to Strict or Lax, or if the Secure flag is present.
    Affected if Cookies lack SameSite or Secure attributes and no other CSRF protection is observed

You are affected if IBM Concert for Z hub component is running with a version between 1.0.0 and 2.1.0 and the application lacks anti-CSRF token validation on state-changing requests.

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 2.2.0 or later
Fixed in 2.2.0
Interim mitigation

Implement anti-CSRF protection by adding unique CSRF tokens to all state-changing requests and validating the Origin/Referer headers server-side, or enable SameSite cookie attributes.

Recommended fix High confidence

IBM Concert 2.2.0 or later

  1. 1. Identify the current IBM Concert installation version by checking the product documentation or system inventory.
  2. 2. Review the IBM Concert 2.2.0 release notes for the CSRF vulnerability fix and any migration considerations.
  3. 3. Create a backup of the current IBM Concert configuration and data.
  4. 4. Schedule a maintenance window for the upgrade process.
  5. 5. Download IBM Concert version 2.2.0 or later from IBM Fix Central or the IBM Concert distribution channel.
  6. 6. Follow IBM's standard upgrade procedure for Concert, which typically involves stopping the Concert services, running the upgrade installer, and verifying the installation.
  7. 7. After upgrade, verify that the CSRF protection is functioning by checking that anti-CSRF tokens are required for state-changing operations.
  8. 8. Test critical workflows to ensure the upgrade did not break existing functionality.
Caveat Review release notes for any breaking changes between 1.0.0-2.1.0 and 2.2.0; minor version upgrades typically have minimal breaking changes but configuration adjustments may be needed

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

Fix this in Concert Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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