{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-0539 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0539 is a medium-severity server-side request forgery vulnerability in Octopus Octopus Server, published on 10 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-0539 and fix it if it is affected.\n\nWhat it is: CVE-2025-0539 is a medium-severity server-side request forgery vulnerability in Octopus Octopus Server, published on 10 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-0539 in the wild and no public exploit code.\n\nAffected product: Octopus Octopus Server. 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-0539/ (Markdown: https://insights.sbomify.com/CVE-2025-0539/index.md)","id":"CVE-2025-0539","markdown":"https://insights.sbomify.com/CVE-2025-0539/index.md","name":"CVE-2025-0539","record":{"aliases":["GHSA-5h88-xc4r-2q76"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Octopus Server","requires_auth":"low_privilege","summary":"An attacker can force Octopus Server to send authenticated requests, potentially compromising the server account and underlying infrastructure.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Octopus","cpe":[{"product":"octopus_server","vendor":"octopus"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"In affected Microsoft Windows versions of Octopus Deploy, the server can be coerced into sending server-side requests that contain authentication material allowing a suitably positioned attacker to compromise the account running Octopus Server and potentially the host infrastructure itself.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Server-side request forgery in Octopus Server","id":"CVE-2025-0539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"octopus:octopus_server","products":["octopus:octopus_server"],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"itsourcecode Tailoring Management System expadd.php sql injection","id":"CVE-2025-0540"},"packages":[],"prev":{"headline":"code-projects Tourism Management System manage-pages.php cross site scripting","id":"CVE-2025-0538"},"products":["Octopus Server"],"published":"2025-04-10","related":[{"cvss_score":9.8,"headline":"Auth bypass in Octopus Server","id":"CVE-2022-2572","kev_date_added":null,"published":"2022-11-01"},{"cvss_score":9.8,"headline":"Security feature bypass in Octopus Server","id":"CVE-2022-2778","kev_date_added":null,"published":"2022-09-30"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-11320","kev_date_added":null,"published":"2018-05-21"},{"cvss_score":9.1,"headline":"Auth bypass in Octopus Server","id":"CVE-2022-2782","kev_date_added":null,"published":"2022-10-26"},{"cvss_score":8.8,"headline":"Race condition in Octopus Server","id":"CVE-2024-2975","kev_date_added":null,"published":"2024-04-09"},{"cvss_score":8.8,"headline":"Command injection in Octopus Server","id":"CVE-2022-4009","kev_date_added":null,"published":"2023-03-16"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2018-18850","kev_date_added":null,"published":"2018-10-31"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["Octopus Deploy"]},"summary":"An attacker can force Octopus Server to send authenticated requests, potentially compromising the server account and underlying infrastructure.","url":"https://insights.sbomify.com/CVE-2025-0539/"}