{"answers":{"affected":"2 open source packages ship an affected version, including studio-42/elfinder.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81889 exists.","fix":"Upgrade studio-42/elfinder to 2.1.70 or later.","what":"CVE-2026-81889 is a high-severity server-side request forgery vulnerability in Studio-42 elFinder, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81889 and fix it if it is affected.\n\nWhat it is: CVE-2026-81889 is a high-severity server-side request forgery vulnerability in Studio-42 elFinder, published on 31 Aug 2026. 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-2026-81889 exists.\n\nAffected packages and fixed versions:\n- studio-42/elfinder (Packagist): affected all versions; fixed in 2.1.70\n- studio-42/elfinder (Packagist): affected all versions; fixed in 2.1.70\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-81889/ (Markdown: https://insights.sbomify.com/CVE-2026-81889/index.md)","id":"CVE-2026-81889","markdown":"https://insights.sbomify.com/CVE-2026-81889/index.md","name":"CVE-2026-81889","record":{"aliases":["GHSA-8x3q-jpjh-qh5c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Web file manager","requires_auth":"none","summary":"Attackers can bypass SSRF protections via DNS rebinding to read internal network resources through elFinder's URL upload feature.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"elFinder is an open-source file manager for web, written in JavaScript using jQuery UI. Prior to 2.1.70, elFinder URL uploads in php/elFinder.class.php can bypass server-side request forgery protections when PHP cURL is unavailable because validate_address() validates $info['ip'], but get_remote_contents() selects fsock_get_contents(), which connects to $arr['host'] and performs a second DNS resolution. An attacker able to submit a URL upload can use DNS rebinding to have the first resolution return a public address and the connection resolution return a loopback or private address, causing the internal HTTP response body to be stored as an uploaded file and made readable through elFinder. After a successful fetch, get_headers($url, true) separately requests the original hostname without reusing the validated and pinned connection, creating an additional blind server-side request forgery path even when curl_get_contents() is selected. This issue is fixed in version 2.1.70.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"elFinder: SSRF protection bypass via DNS rebinding in the `fsock_get_contents()` fallback","id":"CVE-2026-81889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"elFinder: CSRF in netmount allows forced FTP mounts and server-side FTP connections","id":"CVE-2026-81890"},"packages":[{"ecosystem":"Packagist","fixed":["2.1.70"],"introduced":["0"],"last_affected":[],"package":"studio-42/elfinder","purl":null,"source":"GHSA-8x3q-jpjh-qh5c"},{"ecosystem":"Packagist","fixed":["2.1.70"],"introduced":["0"],"last_affected":[],"package":"studio-42/elfinder","purl":"pkg:composer/studio-42/elfinder","source":"GHSA-8x3q-jpjh-qh5c"}],"prev":{"headline":"@hono/oauth-providers: OAuth state check fails open on omitted state, enabling login CSRF and forced account linking","id":"CVE-2026-81888"},"products":["elFinder"],"published":"2026-08-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2026-09-03","vendors":["Studio-42"]},"summary":"Attackers can bypass SSRF protections via DNS rebinding to read internal network resources through elFinder's URL upload feature.","url":"https://insights.sbomify.com/CVE-2026-81889/"}