dbcve.org
Bdr SuiteApplication · Vembu

CVE-2021-26471

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, the http API located at /sgwebservice_o.php accepts a command argument. Using this command argument an unauthenticated attacker can execute arbitrary shell commands.

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 before 4.2.0.1 contain an unauthenticated command injection vulnerability in the /sgwebservice_o.php HTTP API endpoint. The API accepts a command argument that is not properly sanitized, allowing remote attackers to execute arbitrary shell commands on the affected system without any authentication.

MitigationUpgrade to VembuBDR or VembuOffsiteDR version 4.2.0.1 or later to obtain the patch. If immediate upgrade is not possible, restrict network access to the vulnerable API endpoint as a temporary compensating control.

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. Confirm Vembu product is installed
    Locate the Vembu BDR Suite or Vembu Offsite DR installation on the system. Check for the software in installed programs, services, or the installation directory.
    Affected if The system has Vembu BDR Suite or Vembu Offsite DR installed.
  2. Identify installed version
    Check the installed version of VembuBDR or VembuOffsiteDR through the product's UI, about section, or version file. Compare the version number to 4.2.0.1.
    Affected if The installed version is earlier than 4.2.0.1.
  3. Check for web service availability
    Determine if the web service component is running. Look for the web server (typically on port 6060 or 80) that hosts the Vembu web interface.
    Affected if The Vembu web service is running and accessible.
  4. Verify vulnerable endpoint exists
    Send an HTTP request to /sgwebservice_o.php on the Vembu web server. For example: http://TARGET:PORT/sgwebservice_o.php
    Affected if The endpoint responds with any HTTP status, indicating it is exposed.

The environment is affected if Vembu BDR Suite or Vembu Offsite DR version earlier than 4.2.0.1 is installed and the /sgwebservice_o.php web endpoint is accessible on the network.

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 obtain the patch. If immediate upgrade is not possible, restrict network access to the vulnerable API endpoint as a temporary compensating control.

Recommended fix High confidence

4.2.0.1

  1. Back up all critical data and configuration files for the current VembuBDR or VembuOffsiteDR installation
  2. Download VembuBDR version 4.2.0.1 or later from the official vendor source
  3. Stop all Vembu services before beginning the upgrade process
  4. Upgrade the installation to version 4.2.0.1 following the vendor's official upgrade documentation
  5. Restart Vembu services after the upgrade completes
  6. Verify the upgrade was successful by confirming the version number in the management interface
  7. Test that normal backup and restore operations function correctly

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

Fix this in Bdr Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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