{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-116210 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-116210 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-116210 is a high-severity vulnerability in Webasyst Framework, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-116210 and fix it if it is affected.\n\nWhat it is: CVE-2026-116210 is a high-severity vulnerability in Webasyst Framework, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-116210 in the wild and no public exploit code.\n\nAffected product: Webasyst Framework. 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-116210/ (Markdown: https://insights.sbomify.com/CVE-2026-116210/index.md)","id":"CVE-2026-116210","markdown":"https://insights.sbomify.com/CVE-2026-116210/index.md","name":"CVE-2026-116210","record":{"aliases":["GHSA-j7f6-9r44-r4f9"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Webasyst Framework through 4.4.0 contains a cross-site request forgery vulnerability in the Photos app that allows remote attackers to perform backend actions because the app does not enable the framework's opt-in CSRF check. Attackers can lure logged-in Photos users to a malicious page that submits forged POST requests to photo/delete, album/save, photo/manageAccessSave or photo/saveField, deleting photos and changing access rights.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Webasyst Framework through 4.4.0 Photos App CSRF via Backend Actions","id":"CVE-2026-116210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"YesWiki 4.5.0 before 4.7.0 SQL Injection via date_maj_fiche in Bazar entry create","id":"CVE-2026-116211"},"packages":[],"prev":{"headline":"YesWiki 4.6.2 before 4.7.0 Missing Authorization in ActivityPub syncActorPosts","id":"CVE-2026-116208"},"products":["Webasyst Framework"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-26","vendors":["Webasyst"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-116210/"}