dbcve.org
Bdr SuiteApplication · Vembu

CVE-2021-26472

CRITICAL · 9.8 CVSS v3.1 Published 2021-06-08
Fix available
A fix is available. Upgrade to 4.2.0.1 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 VembuBDR before 4.2.0.1 and VembuOffsiteDR before 4.2.0.1 installed on Windows, the http API located at /consumerweb/secure/download.php. Using this command argument an unauthenticated attacker can execute arbitrary OS commands with SYSTEM privileges.

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

VembuBDR and VembuOffsiteDR versions before 4.2.0.1 contain a command injection vulnerability in the /consumerweb/secure/download.php HTTP API endpoint on Windows. An unauthenticated attacker can inject arbitrary OS commands through this API argument, which are executed with SYSTEM-level privileges, providing complete remote code execution over the affected system.

MitigationUpgrade to VembuBDR or VembuOffsiteDR version 4.2.0.1 or later to remediate this vulnerability. If immediate patching is not possible, disable or restrict network access to the web API endpoint and implement additional network segmentation controls.

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
Bdr SuiteApplication
Affected:< 4.2.0.1
Offsite DrApplication
Affected:< 4.2.0.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
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 Vembu installation
    Check for VembuBDR or VembuOffsiteDR installation directories on Windows systems, typically under C:\Program Files\Vembu or C:\Program Files (x86)\Vembu. Look for folders named 'VembuBDR' or 'VembuOffsiteDR'.
    Affected if The software is installed on the system
  2. Check installed version
    Locate the version information file or check the product's About/Version page in the Vembu application. The version is typically displayed in the GUI under Help > About, or may be found in an installer log or registry entry.
    Affected if The installed version is earlier than 4.2.0.1
  3. Verify web service is running
    Check if the Vembu web service is running by opening Services.msc and looking for 'VembuBDR' or 'VembuOffsiteDR' services, or by attempting to access the web interface on the configured port (typically 80 or 443).
    Affected if The web service is running and the HTTP API is accessible
  4. Confirm endpoint accessibility
    Attempt to reach the vulnerable endpoint by accessing http://<server>/consumerweb/secure/download.php or https://<server>/consumerweb/secure/download.php. If the page loads or responds (even with an error), the endpoint is exposed.
    Affected if The /consumerweb/secure/download.php endpoint is reachable over the network

A system is affected if VembuBDR or VembuOffsiteDR version below 4.2.0.1 is installed with the web service running and the vulnerable API endpoint is network-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 4.2.0.1 or later
Fixed in 4.2.0.1
Interim mitigation

Upgrade to VembuBDR or VembuOffsiteDR version 4.2.0.1 or later to remediate this vulnerability. If immediate patching is not possible, disable or restrict network access to the web API endpoint and implement additional network segmentation controls.

Recommended fix High confidence

VembuBDR 4.2.0.1 and VembuOffsiteDR 4.2.0.1

  1. 1. Download VembuBDR version 4.2.0.1 or later from the official Vembu website
  2. 2. Download VembuOffsiteDR version 4.2.0.1 or later from the official Vembu website
  3. 3. Schedule a maintenance window to apply the updates
  4. 4. Back up current configuration and database before upgrading
  5. 5. Stop all Vembu services
  6. 6. Install the updated VembuBDR 4.2.0.1
  7. 7. Install the updated VembuOffsiteDR 4.2.0.1
  8. 8. Restart Vembu services

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

Fix this in Bdr Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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