{"answers":{"affected":"2 open source packages ship an affected version, including apostrophe.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45012 exists.","fix":"No fix has been published for CVE-2026-45012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45012 is a high-severity server-side request forgery vulnerability in apostrophecms apostrophe, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45012 and fix it if it is affected.\n\nWhat it is: CVE-2026-45012 is a high-severity server-side request forgery vulnerability in apostrophecms apostrophe, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45012 exists.\n\nAffected packages and fixed versions:\n- apostrophe (npm): affected all versions up to 4.29.0; no fix listed\n- apostrophe (npm): affected all versions up to 4.29.0; no fix listed\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-45012/ (Markdown: https://insights.sbomify.com/CVE-2026-45012/index.md)","id":"CVE-2026-45012","markdown":"https://insights.sbomify.com/CVE-2026-45012/index.md","name":"CVE-2026-45012","record":{"aliases":["GHSA-pr28-mf3q-qpg6"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js CMS","requires_auth":"low_privilege","summary":"Authenticated attackers can trigger server-side requests to internal or external URLs via rich-text widget imports, potentially exfiltrating data or executing code.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"ApostropheCMS is an open-source Node.js content management system. Versions up to and including 4.29.0 contain an authenticated server-side request forgery (SSRF) in the rich-text widget import flow. An authenticated user who can submit/edit rich-text widget content can cause the server to fetch attacker-controlled URLs during widget validation. For image-compatible responses, the fetched content can be persisted and re-hosted by Apostrophe, allowing response exfiltration. As of time of publication, no known patched versions are available.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Apostrophe has authenticated SSRF in rich-text widget import via @apostrophecms/area/validate-widget","id":"CVE-2026-45012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Apostrophe has a Weak Password Recovery Mechanism for Forgotten Password and Improper Input Validation","id":"CVE-2026-45013"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.29.0"],"package":"apostrophe","purl":null,"source":"GHSA-pr28-mf3q-qpg6"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.29.0"],"package":"apostrophe","purl":"pkg:npm/apostrophe","source":"GHSA-pr28-mf3q-qpg6"}],"prev":{"headline":"Apostrophe has stored XSS via javascript: URL in Image Widget Link","id":"CVE-2026-45011"},"products":["apostrophe"],"published":"2026-06-12","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-15","vendors":["apostrophecms"]},"summary":"Authenticated attackers can trigger server-side requests to internal or external URLs via rich-text widget imports, potentially exfiltrating data or executing code.","url":"https://insights.sbomify.com/CVE-2026-45012/"}