{"answers":{"affected":"2 open source packages ship an affected version, including badaso/core. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52353 exists.","fix":"No fix has been published for CVE-2025-52353 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52353 is a critical vulnerability in n/a, published on 26 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-52353 and fix it if it is affected.\n\nWhat it is: CVE-2025-52353 is a critical vulnerability in n/a, published on 26 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-52353 exists.\n\nAffected packages and fixed versions:\n- badaso/core (Packagist): affected all versions up to 2.9.11; no fix listed\n- badaso/core (Packagist): affected all versions up to 2.9.11; 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-2025-52353/ (Markdown: https://insights.sbomify.com/CVE-2025-52353/index.md)","id":"CVE-2025-52353","markdown":"https://insights.sbomify.com/CVE-2025-52353/index.md","name":"CVE-2025-52353","record":{"aliases":["GHSA-gqp9-jh35-439m"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Badaso CMS","requires_auth":"none","summary":"Authenticated attackers can upload malicious PHP files to Badaso CMS, leading to arbitrary code execution and full host compromise.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"badaso","vendor":"uatech"}],"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 code execution vulnerability in Badaso CMS 2.9.11. The Media Manager allows authenticated users to upload files containing embedded PHP code via the file-upload endpoint, bypassing content-type validation. When such a file is accessed via its URL, the server executes the PHP payload, enabling an attacker to run arbitrary system commands and achieve full compromise of the underlying host. This has been demonstrated by embedding a backdoor within a PDF and renaming it with a .php extension.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Badaso CMS file upload vulnerability","id":"CVE-2025-52353","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-52357"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["2.9.11"],"package":"badaso/core","purl":null,"source":"GHSA-gqp9-jh35-439m"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["2.9.11"],"package":"badaso/core","purl":"pkg:composer/badaso/core","source":"GHSA-gqp9-jh35-439m"}],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-52352"},"products":["n/a"],"published":"2025-08-26","related":[{"cvss_score":9.8,"headline":"Badaso vulnerable to Remote Code Execution (RCE)","id":"CVE-2022-41705","kev_date_added":null,"published":"2022-11-25"},{"cvss_score":9.8,"headline":"Badaso vulnerable to Remote Code Execution via malicious file upload","id":"CVE-2022-41711","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":6.3,"headline":"Uasoft badaso Token BadasoAuthController.php forgetPassword password recovery","id":"CVE-2025-15398","kev_date_added":null,"published":"2025-12-31"},{"cvss_score":5.4,"headline":"Badaso vulnerable to cross-site scripting","id":"CVE-2023-38970","kev_date_added":null,"published":"2023-08-30"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2023-38971","kev_date_added":null,"published":"2023-08-29"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2023-38969","kev_date_added":null,"published":"2023-08-28"}],"sources":[{"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":"2025-08-28","vendors":["n/a"]},"summary":"Authenticated attackers can upload malicious PHP files to Badaso CMS, leading to arbitrary code execution and full host compromise.","url":"https://insights.sbomify.com/CVE-2025-52353/"}