{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50707 exists.","fix":"No fix has been published for CVE-2025-50707 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-50707 is a critical code injection vulnerability in n/a, published on 5 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-50707 and fix it if it is affected.\n\nWhat it is: CVE-2025-50707 is a critical code injection vulnerability in n/a, published on 5 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-50707 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-50707/ (Markdown: https://insights.sbomify.com/CVE-2025-50707/index.md)","id":"CVE-2025-50707","markdown":"https://insights.sbomify.com/CVE-2025-50707/index.md","name":"CVE-2025-50707","record":{"aliases":["GHSA-qpr7-wmfw-r5cr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ThinkPHP framework","requires_auth":"none","summary":"Remote attackers can execute arbitrary code in ThinkPHP3 via the index.php component, requiring immediate framework upgrades.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"thinkphp","vendor":"thinkphp"}],"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-94","name":"Improper Control of Generation of Code"}],"description":"An issue in thinkphp3 v.3.2.5 allows a remote attacker to execute arbitrary code via the index.php component","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":"Code injection in n/a","id":"CVE-2025-50707","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-50708"},"packages":[],"prev":{"headline":"ThinkPHP Path Traversal Vulnerability","id":"CVE-2025-50706"},"products":["n/a"],"published":"2025-08-05","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-63888","kev_date_added":null,"published":"2025-11-20"},{"cvss_score":9.8,"headline":"ThinkPHP Path Traversal Vulnerability","id":"CVE-2025-50706","kev_date_added":null,"published":"2025-08-05"},{"cvss_score":9.8,"headline":"ThinkPHP deserialization vulnerability","id":"CVE-2024-48112","kev_date_added":null,"published":"2024-10-30"},{"cvss_score":9.8,"headline":"ThinkPHP deserialization vulnerability","id":"CVE-2024-44902","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":9.8,"headline":"Deserialization of Untrusted Data in thinkphp","id":"CVE-2022-45982","kev_date_added":null,"published":"2023-02-08"},{"cvss_score":9.8,"headline":"ThinkPHP Framework vulnerable to remote code execution","id":"CVE-2022-47945","kev_date_added":null,"published":"2022-12-23"}],"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":"2025-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code in ThinkPHP3 via the index.php component, requiring immediate framework upgrades.","url":"https://insights.sbomify.com/CVE-2025-50707/"}