{"answers":{"affected":"3 open source packages ship an affected version, including ghost. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-27139 exists.","fix":"Upgrade ghost to 4.39.1 or later.","what":"CVE-2022-27139 is a critical vulnerability in n/a, published on 12 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-27139 and fix it if it is affected.\n\nWhat it is: CVE-2022-27139 is a critical vulnerability in n/a, published on 12 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-27139 exists.\n\nAffected packages and fixed versions:\n- ghost (Bitnami): affected from 4.39.0; fixed in 4.39.1\n- ghost (npm): affected all versions up to 4.39.0; no fix listed\n- ghost (npm): affected all versions up to 4.39.0; no fix listed\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-2022-27139/ (Markdown: https://insights.sbomify.com/CVE-2022-27139/index.md)","id":"CVE-2022-27139","markdown":"https://insights.sbomify.com/CVE-2022-27139/index.md","name":"CVE-2022-27139","record":{"aliases":["BIT-ghost-2022-27139","GHSA-fvc6-qjp7-m4g4"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Ghost CMS","requires_auth":"none","summary":"Attackers with trusted authenticated access can upload crafted SVG files, potentially leading to client-side script execution, though vendor disputes server-side RCE.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ghost","vendor":"ghost"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"An arbitrary file upload vulnerability in the file upload module of Ghost v4.39.0 allows attackers to execute arbitrary code via a crafted SVG file. NOTE: Vendor states that as outlined in Ghost's security documentation, upload of SVGs is only possible by trusted authenticated users. The uploading of SVG files to Ghost does not represent a remote code execution vulnerability. SVGs are not executable on the server, and may only execute javascript in a client's browser - this is expected and intentional functionality","ecosystems":["Bitnami","npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Arbitrary file upload in Ghost","id":"CVE-2022-27139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2022-27140"},"packages":[{"ecosystem":"Bitnami","fixed":["4.39.1"],"introduced":["4.39.0"],"last_affected":[],"package":"ghost","purl":"pkg:bitnami/ghost","source":"BIT-ghost-2022-27139"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.39.0"],"package":"ghost","purl":null,"source":"GHSA-fvc6-qjp7-m4g4"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.39.0"],"package":"ghost","purl":"pkg:npm/ghost","source":"GHSA-fvc6-qjp7-m4g4"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-27135"},"products":["n/a"],"published":"2022-04-12","related":[{"cvss_score":9.8,"headline":"Arbitrary file upload in Ghost","id":"CVE-2022-28397","kev_date_added":null,"published":"2022-04-12"},{"cvss_score":9.6,"headline":"ghost vulnerable to unauthorized newsletter modification via improper access controls","id":"CVE-2022-41654","kev_date_added":null,"published":"2022-12-23"},{"cvss_score":9.4,"headline":"Ghost has a SQL Injection in its Content API","id":"CVE-2026-26980","kev_date_added":null,"published":"2026-02-20"},{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2024-34451","kev_date_added":null,"published":"2024-06-16"},{"cvss_score":9,"headline":"Ghost has possible Cross-site Scripting issue","id":"CVE-2024-23724","kev_date_added":null,"published":"2024-02-11"},{"cvss_score":9,"headline":"Cross-site scripting in Ghost","id":"CVE-2022-47194","kev_date_added":null,"published":"2023-01-19"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers with trusted authenticated access can upload crafted SVG files, potentially leading to client-side script execution, though vendor disputes server-side RCE.","url":"https://insights.sbomify.com/CVE-2022-27139/"}