{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70151 exists.","fix":"No fix has been published for CVE-2025-70151 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70151 is a high-severity vulnerability in n/a, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-70151 and fix it if it is affected.\n\nWhat it is: CVE-2025-70151 is a high-severity vulnerability in n/a, published on 18 Feb 2026. 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-2025-70151 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-70151/ (Markdown: https://insights.sbomify.com/CVE-2025-70151/index.md)","id":"CVE-2025-70151","markdown":"https://insights.sbomify.com/CVE-2025-70151/index.md","name":"CVE-2025-70151","record":{"aliases":["GHSA-8rqj-9226-cwx7"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Scholars Tracking System","requires_auth":"low_privilege","summary":"An authenticated attacker can achieve remote code execution by uploading a malicious PHP file to the web-accessible uploads directory.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"scholars_tracking_system","vendor":"fabian"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"code-projects Scholars Tracking System 1.0 allows an authenticated attacker to achieve remote code execution via unrestricted file upload. The endpoints update_profile_picture.php and upload_picture.php store uploaded files in a web-accessible uploads/ directory using the original, user-supplied filename without validating the file type or extension. By uploading a PHP file and then requesting it from /uploads/, an attacker can execute arbitrary PHP code as the web server user.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2025-70151","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-70152"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-70150"},"products":["n/a"],"published":"2026-02-18","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-70152","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-24098","kev_date_added":null,"published":"2024-03-05"},{"cvss_score":6.9,"headline":"code-projects Scholars Tracking System delete_user.php sql injection","id":"CVE-2025-14940","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":6.9,"headline":"code-projects Scholars Tracking System delete_post.php sql injection","id":"CVE-2025-14950","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":6.9,"headline":"code-projects Scholars Tracking System home.php sql injection","id":"CVE-2025-14951","kev_date_added":null,"published":"2025-12-19"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["n/a"]},"summary":"An authenticated attacker can achieve remote code execution by uploading a malicious PHP file to the web-accessible uploads directory.","url":"https://insights.sbomify.com/CVE-2025-70151/"}