OpenReplay is a self-hosted session replay suite. In version 1.14.0, due to lack of validation Name field - Account Settings (for registration looks like validation is correct), a bad actor can send emails with HTML injected code to the victims. Bad actors can use this to phishing actions for example. Email is really send from OpenReplay, but bad actors can add there HTML code injected (content spoofing). Please notice that during Registration steps for FullName looks like is validated correct - can not type there, but using this kind of bypass/workaround - bad actors can achieve own goal. As of time of publication, no known fixes or workarounds are available.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
| Link | Tags |
|---|---|
| https://github.com/openreplay/openreplay/security/advisories/GHSA-xpfv-454c-3fj4 | vendor advisory exploit |
| https://bugcrowd.com/vulnerability-rating-taxonomy | third party advisory |
| https://capec.mitre.org/data/definitions/242.html | technical description |
| https://cwe.mitre.org/data/definitions/20.html | technical description |
| https://github.com/openreplay/openreplay/blob/main/api/chalicelib/utils/html/invitation.html#L421 | product |