dbcve.org
Web CentralApplication · Archibus

CVE-2022-28862

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-25
Fix available
A fix is available. Upgrade to 26.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 before 26.2, multiple SQL Injection vulnerabilities occur in dwr/call/plaincall/workflow.runWorkflowRule.dwr. Through the injection of arbitrary SQL statements, a potential attacker can modify query syntax and perform unauthorized (and unexpected) operations against the remote database. This is fixed in all recent versions, such as version 26.2.

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

Multiple SQL injection vulnerabilities exist in Archibus Web Central before version 26.2 in the dwr/call/plaincall/workflow.runWorkflowRule.dwr endpoint. Attackers can inject arbitrary SQL statements to modify query syntax and perform unauthorized database operations.

MitigationUpgrade Archibus Web Central to version 26.2 or later to remediate the SQL injection vulnerabilities.

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:< 26.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Archibus Web Central is installed
    Check for the presence of Archibus Web Central application files in your web server's document root or application directory. Look for common installation paths such as /archibus, /webcentral, or similar directories under your web server's htdocs or webapps folder.
    Affected if Archibus Web Central files are found on the server
  2. Determine the installed version of Archibus Web Central
    Locate the version information file or check the application properties. Common locations include a version.properties file, the login page footer, or the system's About/Information page within the Archibus Web Central interface. Compare your version against the affected range of versions before 26.2.
    Affected if The installed version is found to be lower than 26.2
  3. Verify if the DWR endpoint is accessible
    Attempt to access the vulnerable endpoint URL pattern: /dwr/call/plaincall/workflow.runWorkflowRule.dwr via HTTP or HTTPS request to your Archibus server. Check if the endpoint responds (even with an error) indicating it exists and is reachable.
    Affected if The DWR endpoint is reachable and responds to requests
  4. Confirm DWR (Direct Web Remoting) is enabled
    Check the web application's configuration files (typically web.xml) for DWR servlet mappings. Look for org.directwebremoting.servlet.DwrServlet or similar DWR-related servlet configurations that enable the DWR functionality.
    Affected if DWR servlet is enabled and configured in the application

Your environment is affected if Archibus Web Central is installed and the installed version is below 26.2 while the DWR endpoint is accessible.

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

Upgrade Archibus Web Central to version 26.2 or later to remediate the SQL injection vulnerabilities.

Recommended fix High confidence

26.2 or later

  1. 1. Identify the current installed version of Archibus Web Central by checking the application version or configuration files.
  2. 2. If the current version is below 26.2, plan for an upgrade to version 26.2 or later.
  3. 3. Before upgrading, perform a full backup of the database and application files.
  4. 4. Obtain the upgrade package from the official Archibus vendor or authorized distributor.
  5. 5. Follow the vendor's documented upgrade procedure, which typically includes: stopping the application server, running the upgrade installer, validating database migrations, and restarting services.
  6. 6. After upgrade, verify that the dwr/call/plaincall/workflow.runWorkflowRule.dwr endpoint is no longer vulnerable by testing with parameterized inputs or using a vulnerability scanner.
  7. 7. Monitor application logs for any suspicious SQL injection attempts.

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

Fix this in Web Central Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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