{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34292 exists.","fix":"No fix has been published for CVE-2025-34292 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34292 is a critical unsafe deserialization vulnerability in BeWelcome Rox, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-34292 and fix it if it is affected.\n\nWhat it is: CVE-2025-34292 is a critical unsafe deserialization vulnerability in BeWelcome Rox, published on 27 Oct 2025. 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-2025-34292 exists.\n\nAffected product: BeWelcome Rox. 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-2025-34292/ (Markdown: https://insights.sbomify.com/CVE-2025-34292/index.md)","id":"CVE-2025-34292","markdown":"https://insights.sbomify.com/CVE-2025-34292/index.md","name":"CVE-2025-34292","record":{"aliases":["GHSA-5j49-q8fx-ph3m"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"BeWelcome Rox","requires_auth":"low_privilege","summary":"Attackers can achieve remote code execution and full site compromise via PHP object injection in Rox by exploiting unsafe deserialization of user-controlled input.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Rox, the software running BeWelcome, contains a PHP object injection vulnerability resulting from deserialization of untrusted data. User-controlled input is passed to PHP's unserialize(): the POST parameter `formkit_memory_recovery` in \\\\RoxPostHandler::getCallbackAction and the 'memory cookie' read by \\\\RoxModelBase::getMemoryCookie (bwRemember). (1) If present, `formkit_memory_recovery` is processed and passed to unserialize(), and (2) restore-from-memory functionality calls unserialize() on the bwRemember cookie value. Gadget chains present in Rox and bundled libraries enable exploitation of object injection to write arbitrary files or achieve remote code execution. Successful exploitation can lead to full site compromise. This vulnerability was remediated with commit c60bf04 (2025-06-16).","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":"BeWelcome/Rox PHP Object Injection RCE","id":"CVE-2025-34292","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"GN4 Publishing System Insecure Direct Object Reference (IDOR) Information Disclosure","id":"CVE-2025-34293"},"packages":[],"prev":{"headline":"Langflow Origin Validation Error","id":"CVE-2025-34291"},"products":["Rox"],"published":"2025-10-27","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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["BeWelcome"]},"summary":"Attackers can achieve remote code execution and full site compromise via PHP object injection in Rox by exploiting unsafe deserialization of user-controlled input.","url":"https://insights.sbomify.com/CVE-2025-34292/"}