{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23626 exists.","fix":"No fix has been published for CVE-2022-23626 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23626 is a high-severity vulnerability in m1k1o blog, published on 8 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23626 and fix it if it is affected.\n\nWhat it is: CVE-2022-23626 is a high-severity vulnerability in m1k1o blog, published on 8 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23626 exists.\n\nAffected product: m1k1o blog. 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-2022-23626/ (Markdown: https://insights.sbomify.com/CVE-2022-23626/index.md)","id":"CVE-2022-23626","markdown":"https://insights.sbomify.com/CVE-2022-23626/index.md","name":"CVE-2022-23626","record":{"aliases":["GHSA-wmqj-5v54-24x4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP blog application","requires_auth":"low_privilege","summary":"Attackers can upload malicious files that bypass image validation checks, potentially leading to remote code execution on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"blog","vendor":"blog_project"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-252","name":"Unchecked Return Value"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"m1k1o/blog is a lightweight self-hosted facebook-styled PHP blog. Errors from functions `imagecreatefrom*` and `image*` have not been checked properly. Although PHP issued warnings and the upload function returned `false`, the original file (that could contain a malicious payload) was kept on the disk. Users are advised to upgrade as soon as possible. There are no known workarounds for this issue.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2022-05-23","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-05-23","kind":"exploitdb","ref":"50943","stars":null,"title":"m1k1o's Blog v.10 - Remote Code Execution (RCE) (Authenticated)"}],"tier":"weaponised"},"has_fix":false,"headline":"Insufficient file checks in m1k1o/blog","id":"CVE-2022-23626","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Inadequate access verification when using proxy commands in ArchiSteamFarm","id":"CVE-2022-23627"},"packages":[],"prev":{"headline":"DoS vulnerability: Malformed Resource Identifiers","id":"CVE-2022-23625"},"products":["blog"],"published":"2022-02-08","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2017-14345","kev_date_added":null,"published":"2017-09-12"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2017-14346","kev_date_added":null,"published":"2017-09-12"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["m1k1o"]},"summary":"Attackers can upload malicious files that bypass image validation checks, potentially leading to remote code execution on the server.","url":"https://insights.sbomify.com/CVE-2022-23626/"}