Converse.js Exposure of Sensitive Information
Published Feb 19, 2018 · Updated Oct 23, 2026 · Also known as GHSA-mv4h-qm24-x4gh
Original summary
Normalized public record · Updated Oct 23, 2026
Converse.js Exposure of Sensitive Information
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Converse.js and Inverse.js through 3.3 allow remote attackers to obtain sensitive information because it is too difficult to determine whether safe publication of private data was configured or even intended. For example, users might have an expectation that chatroom bookmarks are private, but the various interacting software components do not necessarily make that happen.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- GHSA-mv4h-qm24-x4gh
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Feb 19, 2018 · Last refreshed Oct 23, 2026