{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52239 exists.","fix":"No fix has been published for CVE-2025-52239 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52239 is a critical vulnerability in n/a, published on 4 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52239 and fix it if it is affected.\n\nWhat it is: CVE-2025-52239 is a critical vulnerability in n/a, published on 4 Aug 2025. 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-2025-52239 exists.\n\nAffected product: n/a. 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-52239/ (Markdown: https://insights.sbomify.com/CVE-2025-52239/index.md)","id":"CVE-2025-52239","markdown":"https://insights.sbomify.com/CVE-2025-52239/index.md","name":"CVE-2025-52239","record":{"aliases":["GHSA-q4h7-9j45-w69m"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ZKEACMS","requires_auth":"none","summary":"Attackers can execute arbitrary code by uploading a crafted file to the ZKEACMS web application.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zkeacms","vendor":"zkea"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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 ZKEACMS v4.1 allows attackers to execute arbitrary code via a crafted file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2025-52239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2025-52263"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-52237"},"products":["n/a"],"published":"2025-08-04","related":[{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-20670","kev_date_added":null,"published":"2021-09-13"},{"cvss_score":5.4,"headline":"Cross-site Scripting in ZKEACMS","id":"CVE-2022-29362","kev_date_added":null,"published":"2022-05-25"},{"cvss_score":5.3,"headline":"SeriaWei ZKEACMS Event Action System PendingTaskController.cs Edit server-side request forgery","id":"CVE-2025-10764","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":5.3,"headline":"SeriaWei ZKEACMS EventViewerController.cs Download path traversal","id":"CVE-2025-10766","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":5.3,"headline":"ZKEACMS MediaController.cs Proxy server-side request forgery","id":"CVE-2025-10471","kev_date_added":null,"published":"2025-09-15"},{"cvss_score":5.1,"headline":"SeriaWei ZKEACMS SEOSuggestions ZKEACMS.SEOSuggestions.dll server-side request forgery","id":"CVE-2025-10765","kev_date_added":null,"published":"2025-09-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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by uploading a crafted file to the ZKEACMS web application.","url":"https://insights.sbomify.com/CVE-2025-52239/"}