Security readout for executives and security teams
Plain-English summary
hledger before 1.23 had a stored cross-site scripting issue. Malicious values placed into data used by a generated report could later run JavaScript in a viewer's browser. Business impact depends on whether hledger output is produced from untrusted or shared data and viewed in browsers.
Executive priority
Treat as a targeted hygiene fix unless hledger reports are shared broadly or built from untrusted data. Prioritize upgrade in teams handling financial data, shared reports, or browser-rendered outputs from multiple contributors.
Technical view
CVE-2021-46888 is a stored XSS in hledger's toBloodhoundJson before version 1.23. The CVE states attacker-controlled values could be base64-encoded and parsed with atob, enabling JavaScript execution. The source bundle does not provide CVSS, CWE, or detailed affected package metadata.
Likely exposure
Organizations using hledger versions before 1.23 may be exposed. Highest concern is where generated output includes user-controlled ledger values and is opened by other users in a browser. Evidence about affected packaging and deployment modes is incomplete in the provided sources.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation in the wild. Public GitHub issue, pull request, release, and video references indicate public disclosure and fix discussion, but not confirmed operational exploitation.
Researcher notes
The record is sparse: no CVSS, CWE, CPEs, or explicit exploitation statement are provided. Analysis should stay anchored to hledger before 1.23, the toBloodhoundJson stored XSS, and the referenced GitHub issue, pull request, and release.
Mitigation direction
- Inventory hledger use and identify versions before 1.23.
- Upgrade hledger to version 1.23 or later where applicable.
- Review vendor release notes and PR #1663 for exact fix context.
- Avoid processing untrusted ledger data until upgraded or vendor guidance is applied.
- Limit access to generated browser-viewed output where untrusted data may appear.
Validation and detection
- Confirm deployed hledger versions across workstations, servers, and automation.
- Check whether hledger output is generated from shared or untrusted input.
- Verify upgrade completion by recording installed version 1.23 or later.
- Review report-generation workflows that call or depend on toBloodhoundJson.
- Confirm no compensating controls rely on undocumented assumptions.
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-46888 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/simonmichael/hledger/issues/1525CVE reference
- https://github.com/simonmichael/hledger/pull/1663CVE reference
- https://github.com/simonmichael/hledger/releases/tag/1.23CVE reference
- https://www.youtube.com/watch?v=QnRO-VkfIicCVE reference
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.
