{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25262 exists.","fix":"No fix has been published for CVE-2023-25262 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25262 is a high-severity server-side request forgery vulnerability in n/a, published on 28 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-25262 and fix it if it is affected.\n\nWhat it is: CVE-2023-25262 is a high-severity server-side request forgery vulnerability in n/a, published on 28 Mar 2023. 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-2023-25262 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-2023-25262/ (Markdown: https://insights.sbomify.com/CVE-2023-25262/index.md)","id":"CVE-2023-25262","markdown":"https://insights.sbomify.com/CVE-2023-25262/index.md","name":"CVE-2023-25262","record":{"aliases":["GHSA-f289-g9w2-9j5h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Stimulsoft Reporting Designer","requires_auth":"none","summary":"An attacker can exploit SSRF in Stimulsoft Designer to exfiltrate data from internal network machines via server-side requests.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"designer","vendor":"stimulsoft"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Stimulsoft GmbH Stimulsoft Designer (Web) 2023.1.3 is vulnerable to Server Side Request Forgery (SSRF). TThe Reporting Designer (Web) offers the possibility to embed sources from external locations. If the user chooses an external location, the request to that resource is performed by the server rather than the client. Therefore, the server causes outbound traffic and potentially imports data. An attacker may also leverage this behaviour to exfiltrate data of machines on the internal network of the server hosting the Stimulsoft Reporting Designer (Web).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-03-02","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-03-02T07:54:47Z","kind":"github_poc","ref":"https://github.com/trustcves/CVE-2023-25262","stars":0,"title":null}],"tier":"weaponised"},"has_fix":null,"headline":"Server-side request forgery in n/a","id":"CVE-2023-25262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2023-25263"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2023-25261"},"products":["n/a"],"published":"2023-03-28","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-25261","kev_date_added":null,"published":"2023-03-27"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2023-25260","kev_date_added":null,"published":"2023-03-28"},{"cvss_score":5.5,"headline":"Weak cryptography in n/a","id":"CVE-2023-25263","kev_date_added":null,"published":"2023-03-27"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"An attacker can exploit SSRF in Stimulsoft Designer to exfiltrate data from internal network machines via server-side requests.","url":"https://insights.sbomify.com/CVE-2023-25262/"}