{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24736 exists.","fix":"No fix has been published for CVE-2026-24736 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24736 is a critical server-side request forgery vulnerability in squidex, published on 27 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24736 and fix it if it is affected.\n\nWhat it is: CVE-2026-24736 is a critical server-side request forgery vulnerability in squidex, published on 27 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24736 exists.\n\nAffected product: squidex. 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-2026-24736/ (Markdown: https://insights.sbomify.com/CVE-2026-24736/index.md)","id":"CVE-2026-24736","markdown":"https://insights.sbomify.com/CVE-2026-24736/index.md","name":"CVE-2026-24736","record":{"aliases":["GHSA-wxg2-953m-fg2w"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Headless CMS","requires_auth":"high_privilege","summary":"Attackers can exploit unvalidated webhook URLs to perform Server-Side Request Forgery, accessing internal services and reading responses via logs.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"squidex","vendor":"squidex.io"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Squidex is an open source headless content management system and content management hub. Versions of the application up to and including 7.21.0 allow users to define \"Webhooks\" as actions within the Rules engine. The url parameter in the webhook configuration does not appear to validate or restrict destination IP addresses. It accepts local addresses such as 127.0.0.1 or localhost. When a rule is triggered (Either manual trigger by manually calling the trigger endpoint or by a content update or any other triggers), the backend server executes an HTTP request to the user-supplied URL. Crucially, the server logs the full HTTP response in the rule execution log (lastDump field), which is accessible via the API. Which turns a \"Blind\" SSRF into a \"Full Read\" SSRF. As of time of publication, no patched versions are available.","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":"Squidex has Server-Side Request Forgery (SSRF) Issue in Webhook Configuration","id":"CVE-2026-24736","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"jsPDF has a PDF Injection in AcroFormChoiceField which allows Arbitrary JavaScript Execution","id":"CVE-2026-24737"},"packages":[],"prev":{"headline":"Apache Answer: Revision API Improper Access Control leads to Information Disclosure","id":"CVE-2026-24735"},"products":["squidex"],"published":"2026-01-27","related":[{"cvss_score":9.1,"headline":"Remote code execution in Squidex","id":"CVE-2023-46253","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":6.8,"headline":"Cross-Site Scripting (XSS) via postMessage Handler in Squidex","id":"CVE-2023-46252","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":6.8,"headline":"Cross-Site Request Forgery (CSRF) in squidex/squidex","id":"CVE-2023-0642","kev_date_added":null,"published":"2023-02-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2023-24278","kev_date_added":null,"published":"2023-03-18"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2023-46857","kev_date_added":null,"published":"2023-12-07"},{"cvss_score":5.4,"headline":"Stored Cross-site Scripting in Squidex","id":"CVE-2023-46744","kev_date_added":null,"published":"2023-11-07"}],"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-01-28","vendors":["Squidex"]},"summary":"Attackers can exploit unvalidated webhook URLs to perform Server-Side Request Forgery, accessing internal services and reading responses via logs.","url":"https://insights.sbomify.com/CVE-2026-24736/"}