{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0454 exists.","fix":"No fix has been published for CVE-2025-0454 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0454 is a high-severity server-side request forgery vulnerability in significant-gravitas/autogpt, published on 20 Mar 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-0454 and fix it if it is affected.\n\nWhat it is: CVE-2025-0454 is a high-severity server-side request forgery vulnerability in significant-gravitas/autogpt, published on 20 Mar 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-0454 exists.\n\nAffected product: significant-gravitas/autogpt. 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-0454/ (Markdown: https://insights.sbomify.com/CVE-2025-0454/index.md)","id":"CVE-2025-0454","markdown":"https://insights.sbomify.com/CVE-2025-0454/index.md","name":"CVE-2025-0454","record":{"aliases":["GHSA-jg5r-v2h9-wfxx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AutoGPT utility","requires_auth":"none","summary":"Attackers can bypass SSRF protections in AutoGPT's Requests utility using crafted URLs to access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"autogpt_platform","vendor":"agpt"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A Server-Side Request Forgery (SSRF) vulnerability was identified in the Requests utility of significant-gravitas/autogpt versions prior to v0.4.0. The vulnerability arises due to a hostname confusion between the `urlparse` function from the `urllib.parse` library and the `requests` library. A malicious user can exploit this by submitting a specially crafted URL, such as `http://localhost:\\@google.com/../`, to bypass the SSRF check and perform an SSRF attack.","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":"SSRF Check Bypass in Requests Utility in significant-gravitas/autogpt","id":"CVE-2025-0454","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"NetVision Information airPASS - SQL injection","id":"CVE-2025-0455"},"packages":[],"prev":{"headline":"Denial of Service through Batched Queries in GraphQL in mlflow/mlflow","id":"CVE-2025-0453"},"products":["significant-gravitas/autogpt"],"published":"2025-03-20","related":[{"cvss_score":9.4,"headline":"AutoGPT Affected by Remote Code Execution via Dynamic Module Import in Block Loading (__import__)","id":"CVE-2026-26020","kev_date_added":null,"published":"2026-02-12"},{"cvss_score":9.3,"headline":"AutoGPT has SSRF vulnerability in ReadRSSFeedBlock","id":"CVE-2025-62615","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":9.3,"headline":"AutoGPT has SSRF vulnerability in SendDiscordFileBlock","id":"CVE-2025-62616","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":8.8,"headline":"Server-Side Template Injection (SSTI) in significant-gravitas/autogpt","id":"CVE-2025-1040","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.7,"headline":"AutoGPT has a DoS vulnerability in ReadRSSFeedBlock","id":"CVE-2025-32393","kev_date_added":null,"published":"2026-02-05"},{"cvss_score":8.6,"headline":"AutoGPT is Vulnerable to RCE via Disabled Block Execution","id":"CVE-2026-24780","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":8.6,"headline":"AutoGPT allows leakage of cross-domain cookies and protected headers in requests redirect","id":"CVE-2025-31491","kev_date_added":null,"published":"2025-04-14"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["significant-gravitas"]},"summary":"Attackers can bypass SSRF protections in AutoGPT's Requests utility using crafted URLs to access internal resources.","url":"https://insights.sbomify.com/CVE-2025-0454/"}