Security readout for executives and security teams
Plain-English summary
CVE-2021-4307 is a prototype pollution issue in Yomguithereal Baobab through 2.6.0. In affected applications, malicious input may alter shared JavaScript object behavior, potentially affecting confidentiality, integrity, or availability. The provided sources name version 2.6.1 as the fix.
Executive priority
Prioritize remediation where Baobab is present in internet-facing or user-input-heavy applications. This is not KEV-listed in the supplied evidence, but prototype pollution can create broader application impact, so fixing through normal dependency patching should not be deferred indefinitely.
Technical view
The issue is classified as CWE-1321: improperly controlled modification of object prototype attributes. The affected functionality is not identified in the bundle. CVSS v2 is 6.5 with network attack vector, low complexity, single authentication, and partial C/I/A impact. The patch is commit c56639532a923d9a1600fb863ec7551b188b5d19 and release 2.6.1.
Likely exposure
Exposure is most likely in JavaScript applications that directly or transitively depend on Baobab versions 2.0 through 2.6.0 and process attacker-influenced data through that library. Products not using Baobab are not indicated as affected by the supplied sources.
Exploitation context
The bundle states remote attack is possible and the CVSS vector indicates authentication is required. KEV is false, and no cited source in the bundle establishes active exploitation. The vulnerable functionality is described as unknown, so practical exploitability depends on application-specific usage.
Researcher notes
The source bundle lacks the exact vulnerable function and does not provide exploitation evidence. Treat analysis as dependency-focused: identify Baobab use, compare versions, inspect the 2.6.1 patch, and validate application paths that accept untrusted data into Baobab-managed state.
Mitigation direction
- Inventory applications and lockfiles for Baobab versions 2.0 through 2.6.0.
- Upgrade Baobab to version 2.6.1 or later.
- Rebuild and redeploy any application bundling the vulnerable dependency.
- If upgrade is delayed, review vendor guidance and restrict attacker-controlled inputs reaching Baobab usage paths.
Validation and detection
- Confirm dependency manifests and resolved lockfiles no longer reference Baobab 2.6.0 or earlier.
- Verify deployed bundles were rebuilt after the dependency update.
- Run existing unit and regression tests around state-tree input handling.
- Review software composition analysis results for remaining transitive Baobab exposure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1321: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-4307 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:P/I:P/A:P86.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.217627CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.217627CVE reference · signature, permissions-required
- https://github.com/Yomguithereal/baobab/pull/511CVE reference · issue-tracking
- https://github.com/Yomguithereal/baobab/commit/c56639532a923d9a1600fb863ec7551b188b5d19CVE reference · patch
- https://github.com/Yomguithereal/baobab/releases/tag/2.6.1CVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.