CVE-2021-39198
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 · uneditedOroCRM is an open source Client Relationship Management (CRM) application. Affected versions we found to suffer from a vulnerability which could an attacker is able to disqualify any Lead with a Cross-Site Request Forgery (CSRF) attack. There are no workarounds that address this vulnerability and all users are advised to update their package.
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 confidenceOroCRM is vulnerable to a Cross-Site Request Forgery (CSRF) attack that allows an authenticated user to be tricked into disqualifying any Lead in the CRM system through a malicious request.
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>= 3.1.0, <= 3.1.24>= 4.1.0, <= 4.1.15>= 4.2.0, <= 4.2.5CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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.
-
Locate the installed OroCRM versionAccess the OroCRM administration panel and navigate to System > Application Information, or check the composer.json file in the application root directory if you have file system accessAffected if The displayed version falls within >= 3.1.0 and <= 3.1.24, OR >= 4.1.0 and <= 4.1.15, OR >= 4.2.0 and <= 4.2.5
-
Verify Lead management functionality is presentConfirm that the Lead entity type exists in your OroCRM installation and is accessible to authenticated users through the CRM interfaceAffected if The Lead feature is enabled and users have access to view and manage Lead records
-
Confirm user authentication is possibleVerify that user authentication is enabled and users can log into the OroCRM systemAffected if The application allows user login and maintains authenticated sessions, which is required for the CSRF attack to target authenticated users
Your environment is affected if the installed OroCRM version falls within any of the three vulnerable version ranges AND the Lead management feature is accessible to authenticated users in your installation.
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 · scopedUpdate to the patched version of OroCRM as specified in the vendor advisory; no workarounds are available.
Minimum fixed versions: 3.1.25, 4.1.16, or 4.2.6 (choose the appropriate branch for your installation)
- 1. Identify which major.minor version branch your installation is running (3.1.x, 4.1.x, or 4.2.x)
- 2. For 3.1.x branch: upgrade to version 3.1.25 or later
- 3. For 4.1.x branch: upgrade to version 4.1.16 or later
- 4. For 4.2.x branch: upgrade to version 4.2.6 or later
- 5. Verify the upgrade was successful and test that the Lead disqualification functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-39198 — 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-39198 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