{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8378 exists.","fix":"No fix has been published for CVE-2024-8378 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-8378 is a medium-severity vulnerability in Unknown Safe SVG, published on 7 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-8378 and fix it if it is affected.\n\nWhat it is: CVE-2024-8378 is a medium-severity vulnerability in Unknown Safe SVG, published on 7 Nov 2024. An attacker needs administrator access to exploit it, 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-2024-8378 exists.\n\nAffected product: Unknown Safe SVG. 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-2024-8378/ (Markdown: https://insights.sbomify.com/CVE-2024-8378/index.md)","id":"CVE-2024-8378","markdown":"https://insights.sbomify.com/CVE-2024-8378/index.md","name":"CVE-2024-8378","record":{"aliases":["GHSA-j7hj-68jp-pg28"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"An attacker can bypass SVG sanitization in the Safe SVG WordPress plugin by using specific upload methods, potentially leading to code execution.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"safe_svg","vendor":"10up"}],"cvss":{"score":4.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"The Safe SVG WordPress plugin before 2.2.6 has its sanitisation code is only running for paths that call wp_handle_upload, but not for example for code that uses wp_handle_sideload which is often used to upload attachments via raw POST data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Safe SVG \u003c 2.2.6 - Author+ SVG Sanitisation Bypass","id":"CVE-2024-8378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cost Calculator Builder \u003c 3.2.29 - Admin+ SQL Injection","id":"CVE-2024-8379"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-8377"},"products":["Safe SVG"],"published":"2024-11-07","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-18854","kev_date_added":null,"published":"2019-11-11"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-18855","kev_date_added":null,"published":"2019-11-11"},{"cvss_score":6.1,"headline":"Safe SVG \u003c 1.9.10 - SVG Sanitisation Bypass","id":"CVE-2022-1091","kev_date_added":null,"published":"2022-04-18"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-07","vendors":["Unknown"]},"summary":"An attacker can bypass SVG sanitization in the Safe SVG WordPress plugin by using specific upload methods, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2024-8378/"}