CVE-2021-26474
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 · uneditedVarious Vembu products allow an attacker to execute a (non-blind) http-only Cross Site Request Forgery (Other products or versions of products in this family may be affected too.)
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in various Vembu products allowing authenticated attackers to execute unintended actions on behalf of legitimate users through malicious requests. The non-blind nature of this CSRF means attackers can view the HTTP response of the forged request, increasing exploit potential.
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< 4.2.0= 4.2.0= 4.2.0.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Vembu productCheck system for Vembu Bdr Suite or Vembu Offsite Dr installation. Look for Vembu service processes or installation directories.Affected if Either Vembu Bdr Suite or Vembu Offsite Dr is installed on the system
-
Determine installed version of Vembu productLocate version information in the product interface, about page, or installation logs. Common locations include the web console or application settings.Affected if Version cannot be determined or is lower than 4.2.0 for Bdr Suite, or is exactly 4.2.0 or 4.2.0.1 for Offsite Dr
-
Compare version against affected rangesIf Vembu Bdr Suite is installed, verify version is 4.2.0 or higher to be outside the affected range. If Vembu Offsite Dr is installed, verify version is not 4.2.0 or 4.2.0.1.Affected if Vembu Bdr Suite version is below 4.2.0, OR Vembu Offsite Dr version is exactly 4.2.0 or 4.2.0.1
-
Check for anti-CSRF token implementationInspect state-changing operations in the web interface (such as backup configuration, user management, or policy changes). Submit a test request and verify whether a unique token is required for each state-changing action.Affected if State-changing requests do not require anti-CSRF tokens and can be replayed without validation
Environment is affected if Vembu Bdr Suite below 4.2.0 or Vembu Offsite Dr version 4.2.0/4.2.0.1 is installed AND state-changing operations lack anti-CSRF token validation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.2.0
Implement anti-CSRF tokens for state-changing operations and configure SameSite cookie attributes to prevent cross-origin requests.
Bdr Suite 4.2.0 or later / Offsite Dr 4.2.0.1 or later
- Download the fixed version of Bdr Suite (4.2.0 or later) from the official Vembu vendor site
- Review the vendor's upgrade documentation before proceeding
- Create a full backup of the current configuration and data
- Schedule a maintenance window for the upgrade process
- Stop any running services related to Bdr Suite or Offsite Dr
- Install version 4.2.0 or later following vendor instructions
- Verify the installation was successful
- Test that the application functions normally after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26474 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26474 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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