Activematrix Business Process ManagementApplication · Tibco

CVE-2019-11203

MEDIUM · 6.1 CVSS v3.1 Published 2019-04-24
Fix available
A fix is available. Upgrade to after 4.2.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
The workspace client, openspace client, app development client, and REST API of TIBCO Software Inc.'s TIBCO ActiveMatrix BPM, TIBCO ActiveMatrix BPM Distribution for TIBCO Silver Fabric, and TIBCO Silver Fabric Enabler for ActiveMatrix BPM contain cross site scripting (XSS) and cross-site request forgery vulnerabilities. Affected releases are TIBCO Software Inc.'s TIBCO ActiveMatrix BPM: versions up to and including 4.2.0, TIBCO ActiveMatrix BPM Distribution for TIBCO Silver Fabric: versions up to and including 4.2.0, and TIBCO Silver Fabric Enabler for ActiveMatrix BPM: versions up to and including 1.4.1.

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

TIBCO ActiveMatrix BPM contains reflected XSS and CSRF vulnerabilities in multiple client interfaces (workspace, openspace, app development) and the REST API. Attackers can inject malicious scripts via unsanitized inputs or forge requests by tricking authenticated users, potentially leading to session hijacking or unauthorized actions.

MitigationUpgrade to TIBCO ActiveMatrix BPM version 4.2.1 or later (and corresponding Silver Fabric Enabler updates). Implement input validation, output encoding, and CSRF tokens as compensating controls until patching is feasible.

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
Activematrix Business Process ManagementApplication
Affected:<= 4.2.0
Silver Fabric EnablerApplication
Affected:<= 1.4.1

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 ActiveMatrix BPM version
    Locate and inspect the TIBCO ActiveMatrix BPM installation directory and check the version manifest or product info file. Common locations include the installation root or version.properties file within the product distribution.
    Affected if The installed version is 4.2.0 or lower (any version <= 4.2.0)
  2. Identify Silver Fabric Enabler version
    Locate and inspect the TIBCO Silver Fabric Enabler installation and check its version information file or product metadata.
    Affected if The installed version is 1.4.1 or lower (any version <= 1.4.1)
  3. Determine if workspace interface is exposed
    Check if the BPM workspace web interface is accessible on the network. This is typically served over HTTP/HTTPS on the configured application server port.
    Affected if The workspace interface is accessible and the BPM version is <= 4.2.0
  4. Determine if openspace or app development interfaces are exposed
    Check if the openspace or application development client interfaces are accessible. These are additional client access points in the affected product.
    Affected if Either openspace or app development interfaces are accessible and the BPM version is <= 4.2.0
  5. Determine if REST API is enabled
    Check the BPM configuration to see if the REST API endpoints are enabled and accessible. Look for REST API service configuration in the product settings.
    Affected if REST API is enabled and accessible, and the BPM version is <= 4.2.0

The environment is affected if TIBCO ActiveMatrix BPM is at version 4.2.0 or lower OR Silver Fabric Enabler is at version 1.4.1 or lower, and any of the workspace, openspace, app development, or REST API interfaces are exposed to users or networks where the vulnerability could be exploited.

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.

From vendor data
Upgrade available Upgrade to a release after 4.2.0
Interim mitigation

Upgrade to TIBCO ActiveMatrix BPM version 4.2.1 or later (and corresponding Silver Fabric Enabler updates). Implement input validation, output encoding, and CSRF tokens as compensating controls until patching is feasible.

Fix this in Activematrix Business Process Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11203 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11203 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