dbcve.org
Bdr SuiteApplication · Vembu

CVE-2021-26473

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 action logFilePath allows an attacker to write arbitrary files in the context of the web server process. These files can then be executed remotely by calling the file via the web server.

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

The vulnerability exists in the /sgwebservice_o.php API endpoint where the logFilePath action parameter allows unauthenticated attackers to write arbitrary files to the web server's filesystem. These files can then be executed by calling them via the web server, achieving remote code execution.

MitigationUpgrade to VembuBDR version 4.2.0.1 or VembuOffsiteDR version 4.2.0.1. Until patched, implement network-level access controls to restrict access to the sgwebservice_o.php endpoint from untrusted sources.

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 product and version
    Locate the Vembu installation directory and check the version file, or query the web interface for version information. Common paths include C:\Program Files\Vembu\VembuBDR or /opt/vembu/vembubdr. Look for a version.txt, about.php, or similar file that displays the installed version number.
    Affected if The installed version is lower than 4.2.0.1 for either Vembu BDR Suite or Vembu Offsite Dr.
  2. Locate the vulnerable PHP endpoint
    Search for the file sgwebservice_o.php in the web root directory of the Vembu installation. Common web root locations include /html, /htdocs, or the www subdirectory within the Vembu installation path.
    Affected if The file sgwebservice_o.php exists in the web-accessible directory.
  3. Verify the logFilePath action is present
    Open sgwebservice_o.php in a text editor and search for the string 'logFilePath' to confirm the vulnerable parameter handler exists in the code.
    Affected if The code contains a logFilePath action parameter handler.
  4. Check network accessibility of the endpoint
    Attempt to access http://<server>/sgwebservice_o.php from an untrusted network or external IP address. Use a web proxy or curl command to test if the endpoint responds without authentication.
    Affected if The endpoint is reachable from untrusted/networked sources without authentication.

A user is affected if they run Vembu BDR Suite or Vembu Offsite Dr versions below 4.2.0.1 and the sgwebservice_o.php 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 version 4.2.0.1 or VembuOffsiteDR version 4.2.0.1. Until patched, implement network-level access controls to restrict access to the sgwebservice_o.php endpoint from untrusted sources.

Recommended fix High confidence

VembuBDR 4.2.0.1 and VembuOffsiteDR 4.2.0.1

  1. 1. Verify current installation version of VembuBDR or VembuOffsiteDR
  2. 2. Download VembuBDR version 4.2.0.1 or later from the official vendor website
  3. 3. Download VembuOffsiteDR version 4.2.0.1 or later from the official vendor website
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Back up all critical data and configuration files
  6. 6. Apply the upgrade to VembuBDR first, then VembuOffsiteDR
  7. 7. Verify the upgrade was successful by checking the version number
  8. 8. Test that the /sgwebservice_o.php endpoint no longer allows arbitrary file writes

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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-26473 — 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-26473 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