{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56379 exists.","fix":"No fix has been published for CVE-2025-56379 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56379 is a medium-severity cross-site scripting vulnerability in Frappe Erpnext, published on 2 Oct 2025. 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-2025-56379 and fix it if it is affected.\n\nWhat it is: CVE-2025-56379 is a medium-severity cross-site scripting vulnerability in Frappe Erpnext, published on 2 Oct 2025. 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-2025-56379 exists.\n\nAffected product: Frappe Erpnext. 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-2025-56379/ (Markdown: https://insights.sbomify.com/CVE-2025-56379/index.md)","id":"CVE-2025-56379","markdown":"https://insights.sbomify.com/CVE-2025-56379/index.md","name":"CVE-2025-56379","record":{"aliases":["GHSA-5wvf-mfpw-266p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"ERPNext","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts in the blog post feature, potentially compromising user sessions and data.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"erpnext","vendor":"frappe"},{"product":"frappe","vendor":"frappe"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","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-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A stored cross-site scripting (XSS) vulnerability in the blog post feature of ERPNEXT v15.67.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the content field.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-10-01","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-10-01T18:48:11Z","kind":"github_poc","ref":"https://github.com/MoAlali/CVE-2025-56379","stars":0,"title":"A stored cross-site scripting (XSS) vulnerability in the blog post feature of ERPNEXT v15.67.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the content field."}],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2025-56379","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"frappe:erpnext","products":["frappe:erpnext"],"type":"xss","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-56380"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-56365"},"products":["n/a"],"published":"2025-10-02","related":[{"cvss_score":9.9,"headline":"ERPNext: Unauthorised Document modification due to missing validation","id":"CVE-2026-44442","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2026-38431","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-66438","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-66439","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-66440","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":9.6,"headline":"File upload in n/a","id":"CVE-2025-67289","kev_date_added":null,"published":"2025-12-22"},{"cvss_score":9.3,"headline":"ERP: Document access through endpoints due to missing validation","id":"CVE-2026-27471","kev_date_added":null,"published":"2026-02-21"}],"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":"2025-10-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts in the blog post feature, potentially compromising user sessions and data.","url":"https://insights.sbomify.com/CVE-2025-56379/"}