{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33657 exists.","fix":"No fix has been published for CVE-2026-33657 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33657 is a medium-severity cross-site scripting vulnerability in espocrm, published on 13 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-33657 and fix it if it is affected.\n\nWhat it is: CVE-2026-33657 is a medium-severity cross-site scripting vulnerability in espocrm, published on 13 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33657 exists.\n\nAffected product: espocrm. 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-2026-33657/ (Markdown: https://insights.sbomify.com/CVE-2026-33657/index.md)","id":"CVE-2026-33657","markdown":"https://insights.sbomify.com/CVE-2026-33657/index.md","name":"CVE-2026-33657","record":{"aliases":["GHSA-8prm-r5j9-j574"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"EspoCRM application","requires_auth":"low_privilege","summary":"Authenticated users can inject HTML into email notifications via stream notes, enabling phishing and tracking against recipients.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"espocrm","vendor":"espocrm"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"EspoCRM is an open source customer relationship management application. Versions 9.3.3 and below have a stored HTML injection vulnerability that allows any authenticated user with standard (non-administrative) privileges to inject arbitrary HTML into system-generated email notifications by crafting malicious content in the post field of stream activity notes. The vulnerability exists because server-side Handlebars templates render the post field using unescaped triple-brace syntax, the Markdown processor preserves inline HTML by default, and the rendering pipeline explicitly skips sanitization for fields present in additionalData, creating a path where attacker-controlled HTML is accepted, stored, and rendered directly into emails without any escaping. Since the emails are sent using the system's configured SMTP identity (such as an administrative sender address), the injected content appears fully trusted to recipients, enabling phishing attacks, user tracking via embedded resources like image beacons, and UI manipulation within email content. The @mention feature further increases the impact by allowing targeted delivery of malicious emails to specific users. This issue has been fixed in version 9.3.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-05-11","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-11T20:39:31Z","kind":"github_poc","ref":"https://github.com/EntroVyx/CVE-2026-33657","stars":0,"title":"EspoCRM 9.3.3 - Stored HTML Injection in Email Notifications"}],"tier":"weaponised"},"has_fix":false,"headline":"EspoCRM: Stored HTML injection in email notifications about stream notes via unescaped post field","id":"CVE-2026-33657","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Rails Active Storage has a possible DoS vulnerability in proxy mode via multi-range requests","id":"CVE-2026-33658"},"packages":[],"prev":{"headline":"Path traversal in espocrm","id":"CVE-2026-33656"},"products":["espocrm"],"published":"2026-04-13","related":[{"cvss_score":10,"headline":"Path traversal in n/a","id":"CVE-2014-7985","kev_date_added":null,"published":"2014-10-31"},{"cvss_score":9.1,"headline":"Path traversal in espocrm","id":"CVE-2026-33656","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2022-38843","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2019-14351","kev_date_added":null,"published":"2019-07-28"},{"cvss_score":8.6,"headline":"EspoCRM 5.7.0 \u003c 5.9.0 - Two-Factor Authentication Bypass via Auth Token Reuse Between Accounts with Identical Passwords","id":"CVE-2020-37094","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8,"headline":"Code injection in n/a","id":"CVE-2022-38844","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":7.2,"headline":"EspoCRM has Admin TemplateManager path traversal that allows arbitrary file read write and delete","id":"CVE-2026-33733","kev_date_added":null,"published":"2026-04-22"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-13","vendors":["espocrm"]},"summary":"Authenticated users can inject HTML into email notifications via stream notes, enabling phishing and tracking against recipients.","url":"https://insights.sbomify.com/CVE-2026-33657/"}