dbcve.org
Web CentralApplication · Archibus

CVE-2021-41555

MEDIUM · 6.1 CVSS v3.1 Published 2021-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
In ARCHIBUS Web Central 21.3.3.815 (a version from 2014), XSS occurs in /archibus/dwr/call/plaincall/workflow.runWorkflowRule.dwr because the data received as input from clients is re-included within the HTTP response returned by the application without adequate validation. In this way, if HTML code or client-side executable code (e.g., Javascript) is entered as input, the expected execution flow could be altered. This is fixed in all recent versions, such as version 26. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. Version 21.3 was officially de-supported by the end of 2020

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 reflected Cross-Site Scripting (XSS) vulnerability in ARCHIBUS Web Central 21.3.3.815 allows attackers to inject malicious HTML or JavaScript code through the /archibus/dwr/call/plaincall/workflow.runWorkflowRule.dwr endpoint. User-supplied input is returned in the HTTP response without proper validation or encoding, enabling the injected code to execute in victims' browsers.

MitigationUpgrade to a supported version (version 26 or later). If immediate upgrade is not feasible, implement input validation with output encoding at the application layer or deploy a WAF as a compensating control until migration can be completed.

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
Web CentralApplication
Affected:= 21.3.3.815

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. Confirm ARCHIBUS Web Central installation
    Check if the web application is running by accessing the base URL of the server (e.g., http://yourserver/archibus) and look for the ARCHIBUS login page or application interface.
    Affected if ARCHIBUS Web Central is installed and accessible via web browser
  2. Identify installed version
    Locate the version information in the application. Typically found in the login page footer, within the help/about section, or by accessing the system management console. Compare against the affected version 21.3.3.815.
    Affected if Installed version is exactly 21.3.3.815
  3. Verify vulnerable endpoint accessibility
    Attempt to access the endpoint at /archibus/dwr/call/plaincall/workflow.runWorkflowRule.dwr via HTTP request. A 200 OK response indicates the endpoint exists and may be vulnerable.
    Affected if The endpoint returns a valid response (status 200) rather than a 404 or access denied error
  4. Test for reflected input (optional validation)
    Send a benign test string (such as a unique identifier like 'TESTXSS123') as a parameter to the vulnerable endpoint and examine if the same string appears unencoded in the HTTP response.
    Affected if Input is reflected verbatim in the response without HTML encoding or validation

The environment is affected if ARCHIBUS Web Central version 21.3.3.815 is installed and the /archibus/dwr/call/plaincall/workflow.runWorkflowRule.dwr endpoint is accessible and reflects user input without encoding.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a supported version (version 26 or later). If immediate upgrade is not feasible, implement input validation with output encoding at the application layer or deploy a WAF as a compensating control until migration can be completed.

Recommended fix High confidence

Version 26 (or latest supported release)

  1. 1. Back up the current ARCHIBUS Web Central 21.3.3.815 installation, database, and configuration files
  2. 2. Obtain the ARCHIBUS Web Central version 26 (or latest supported version) from the official vendor
  3. 3. Review the official upgrade/migration documentation for transitioning from version 21.x to version 26
  4. 4. Test the upgrade in a non-production environment to verify functionality and identify any compatibility issues
  5. 5. Deploy the upgraded version to production after successful testing
Caveat Upgrading from deprecated version 21.3 to version 26 may introduce breaking changes; thorough testing in a staging environment is recommended before production deployment

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

Fix this in Web Central Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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