{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-48226 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-48226 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-48226 is a medium-severity cross-site scripting vulnerability in openreplay, published on 21 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-48226 and fix it if it is affected.\n\nWhat it is: CVE-2023-48226 is a medium-severity cross-site scripting vulnerability in openreplay, published on 21 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-48226 in the wild and no public exploit code.\n\nAffected product: openreplay. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-48226/ (Markdown: https://insights.sbomify.com/CVE-2023-48226/index.md)","id":"CVE-2023-48226","markdown":"https://insights.sbomify.com/CVE-2023-48226/index.md","name":"CVE-2023-48226","record":{"aliases":["GHSA-xpfv-454c-3fj4"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Session replay suite","requires_auth":"low_privilege","summary":"Attackers can inject HTML into account names to spoof content in legitimate emails, facilitating phishing attacks against users.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openreplay","vendor":"openreplay"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OpenReplay HTML Injection vulnerability","id":"CVE-2023-48226","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Umbraco CMS Backoffice User can bypass \"Publish\" restriction","id":"CVE-2023-48227"},"packages":[],"prev":{"headline":"Laf env causes sensitive information disclosure","id":"CVE-2023-48225"},"products":["openreplay"],"published":"2023-11-21","related":[{"cvss_score":6.9,"headline":"OpenReplay: SQL injection in cards/search via unvalidated sort field parameter","id":"CVE-2026-28443","kev_date_added":null,"published":"2026-03-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["openreplay"]},"summary":"Attackers can inject HTML into account names to spoof content in legitimate emails, facilitating phishing attacks against users.","url":"https://insights.sbomify.com/CVE-2023-48226/"}