{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-55154 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-55154 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55154 is a medium-severity vulnerability in espocrm, published on 15 Oct 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-55154 and fix it if it is affected.\n\nWhat it is: CVE-2026-55154 is a medium-severity vulnerability in espocrm, published on 15 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-55154 in the wild and no public exploit code.\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-55154/ (Markdown: https://insights.sbomify.com/CVE-2026-55154/index.md)","id":"CVE-2026-55154","markdown":"https://insights.sbomify.com/CVE-2026-55154/index.md","name":"CVE-2026-55154","record":{"aliases":["GHSA-xrwp-2gph-985x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"EspoCRM","requires_auth":"low_privilege","summary":"Authenticated users can bypass CSV/XLSX export sanitization to inject formulas, potentially leading to data disclosure or code execution when exported files are opened.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"description":"EspoCRM is an open source customer relationship management application. Prior to 9.3.9, application/Espo/Tools/Export/Format/Csv/Processor.php, application/Espo/Tools/Export/Format/Xlsx/OpenSpoutProcessor.php, and application/Espo/Tools/Export/Format/Xlsx/PhpSpreadsheetProcessor.php inspect only the first byte in sanitizeCellValue(). An authenticated low-privileged user can store a free-text value whose formula trigger is preceded by whitespace or a control character, causing CSV or XLSX export to omit the leading single-quote formula-neutralization prefix. When a privileged user opens the exported file and accepts applicable spreadsheet security prompts, spreadsheet software can ignore the whitespace or control-character prefix and evaluate the cell as a formula, permitting outbound data disclosure and, on legacy configurations with DDE enabled, command execution. This issue is fixed in version 9.3.9.","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":"EspoCRM: CSV/Formula Injection sanitizer bypass via leading whitespace/control characters in export","id":"CVE-2026-55154","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Token Optimizer MCP: Unauthenticated Path Traversal in Dashboard Session Log API Endpoints","id":"CVE-2026-55156"},"packages":[],"prev":{"headline":"mchange-commons-java contains elements susceptible to abuse via JNDI injection and \"deserialization gadgets\"","id":"CVE-2026-55153"},"products":["espocrm"],"published":"2026-10-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["espocrm"]},"summary":"Authenticated users can bypass CSV/XLSX export sanitization to inject formulas, potentially leading to data disclosure or code execution when exported files are opened.","url":"https://insights.sbomify.com/CVE-2026-55154/"}