Security readout for executives and security teams
Plain-English summary
CVE-2021-23432 is a prototype pollution issue in the JavaScript package mootools. If an application lets untrusted data reach Object.merge(), an attacker may influence object behavior and cause limited confidentiality or integrity impact. The public bundle does not show active exploitation or a confirmed fixed version.
Executive priority
Treat as a moderate-priority dependency risk. Prioritize systems that process user-supplied JSON, form data, or client-side state with mootools. Escalate if mootools is internet-facing or difficult to isolate.
Technical view
The issue affects mootools and is caused by unsafe handling of untrusted input in Object.merge(). The CVSS 3.1 score is 5.4, with network attack vector, low complexity, no privileges required, user interaction required, and low confidentiality and integrity impact.
Likely exposure
Exposure is most likely in applications that include mootools directly, through dependency trees, or as vendored browser code, and use Object.merge() on attacker-controlled data. The affected version metadata is incomplete, but the description says all mootools versions are affected.
Exploitation context
The source bundle does not identify CISA KEV listing or active exploitation. The CVSS data indicates proof-of-concept maturity, but no weaponized public exploitation details should be assumed from the provided evidence.
Researcher notes
The bundle lacks CWE mappings and detailed vendor remediation data. Validate affected usage context before scoring internally. User interaction is present in the CVSS vector, and availability impact is listed as none.
Mitigation direction
- Inventory direct, transitive, and vendored mootools usage.
- Check Snyk and project guidance for patched versions or official workarounds.
- Prevent untrusted objects from reaching Object.merge().
- Replace mootools where no maintained fix is available.
- Add regression tests for unsafe merge behavior.
Validation and detection
- Review package manifests, lockfiles, and bundled assets for mootools.
- Identify code paths calling Object.merge() with external input.
- Confirm findings against CVE and Snyk records.
- Verify compensating validation blocks prototype pollution inputs.
- Document exposure decisions and remaining uncertainty.
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.
CVE-2021-23432 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
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N/E: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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- https://snyk.io/vuln/SNYK-JS-MOOTOOLS-1325536CVE reference · x_refsource_MISC
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.
