{"answers":{"affected":"2 open source packages ship an affected version, including nocodb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-28357 in the wild and no public exploit code.","fix":"Upgrade nocodb to 0.301.3 or later.","what":"CVE-2026-28357 is a medium-severity cross-site scripting vulnerability in nocodb, published on 2 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-28357 and fix it if it is affected.\n\nWhat it is: CVE-2026-28357 is a medium-severity cross-site scripting vulnerability in nocodb, published on 2 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-28357 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nocodb (npm): affected all versions; fixed in 0.301.3\n- nocodb (npm): affected all versions; fixed in 0.301.3\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-28357/ (Markdown: https://insights.sbomify.com/CVE-2026-28357/index.md)","id":"CVE-2026-28357","markdown":"https://insights.sbomify.com/CVE-2026-28357/index.md","name":"CVE-2026-28357","record":{"aliases":["GHSA-vx5p-q85x-xm3c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"NocoDB database spreadsheet","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in victim browsers by injecting malicious HTML into Formula cells, potentially leading to session hijacking or data theft.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nocodb","vendor":"nocodb"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to version 0.301.3, a stored XSS vulnerability exists in the Formula virtual cell. Formula results containing URI::() patterns are rendered via v-html without sanitization, allowing injected HTML to execute. This issue has been patched in version 0.301.3.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"NocoDB: Stored Cross-Site Scripting via Formula Cell","id":"CVE-2026-28357","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"NocoDB: User Enumeration via Password Reset Endpoint","id":"CVE-2026-28358"},"packages":[{"ecosystem":"npm","fixed":["0.301.3"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":null,"source":"GHSA-vx5p-q85x-xm3c"},{"ecosystem":"npm","fixed":["0.301.3"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-vx5p-q85x-xm3c"}],"prev":{"headline":"ReDoS in multipart 1.3.0 - `parse_options_header()`","id":"CVE-2026-28356"},"products":["nocodb"],"published":"2026-03-02","related":[{"cvss_score":9.1,"headline":"Server-Side Request Forgery (SSRF) in nocodb/nocodb","id":"CVE-2022-2339","kev_date_added":null,"published":"2022-07-07"},{"cvss_score":9.1,"headline":"Generation of Error Message Containing Sensitive Information in nocodb/nocodb","id":"CVE-2022-2062","kev_date_added":null,"published":"2022-06-13"},{"cvss_score":9.1,"headline":"Insufficient Session Expiration in nocodb/nocodb","id":"CVE-2022-2064","kev_date_added":null,"published":"2022-06-13"},{"cvss_score":9,"headline":"Improper Privilege Management in nocodb/nocodb","id":"CVE-2022-2063","kev_date_added":null,"published":"2022-06-13"},{"cvss_score":9,"headline":"Cross-site Scripting (XSS) - Stored in nocodb/nocodb","id":"CVE-2022-2022","kev_date_added":null,"published":"2022-06-07"},{"cvss_score":8.5,"headline":"NocoDB Vulnerable to Stored Cross-Site Scripting via SVG upload","id":"CVE-2026-24769","kev_date_added":null,"published":"2026-01-28"},{"cvss_score":8,"headline":"NocoDB - CSV Injection in User Management","id":"CVE-2022-22121","kev_date_added":null,"published":"2022-01-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["nocodb"]},"summary":"Attackers can execute arbitrary scripts in victim browsers by injecting malicious HTML into Formula cells, potentially leading to session hijacking or data theft.","url":"https://insights.sbomify.com/CVE-2026-28357/"}