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).
Security readout for executives and security teams
Plain-English summary
Rox, the PHP software behind BeWelcome, had unsafe deserialization of user-controlled data. An attacker with low privileges could potentially turn this into arbitrary file writes or remote code execution. The reported impact is full site compromise. A remediation commit is identified, but version-range details are not clearly expressed in the provided sources.
Executive priority
Prioritize immediately if your organization runs Rox or a derivative exposed to users. The business risk is site takeover and data compromise. If Rox is not present, no direct action is indicated beyond confirming the inventory.
Technical view
CVE-2025-34292 is a CWE-502 PHP object injection issue in Rox. User-controlled values from the formkit_memory_recovery POST parameter and bwRemember memory cookie are passed to unserialize(). Available gadget chains in Rox and bundled libraries can enable arbitrary file write or RCE. CVSS 4.0 score is 9.4, with network access, low complexity, and low privileges required.
Likely exposure
Exposure is likely limited to deployments of BeWelcome Rox that include the vulnerable deserialization paths before commit c60bf04. Public affected-version data is incomplete; the source bundle lists version “0” and default status “unaffected,” which is not enough for precise fleet matching.
Exploitation context
The CVSS vector indicates network exploitation with low complexity, no user interaction, and low privileges. Public sources include a technical write-up tagged as exploit, but CISA KEV is false in the provided data, so active exploitation is not established here.
Researcher notes
The core issue is unsafe PHP unserialize on attacker-influenced POST and cookie values. Sources state gadget chains permit file write or RCE. Avoid assuming broad ecosystem exposure: the record identifies Rox/BeWelcome, but precise affected releases are not clearly documented in the provided bundle.
Mitigation direction
Check whether Rox includes remediation commit c60bf04 from 2025-06-16.
Update Rox to a vendor-maintained revision containing the fix.
Review vendor and project guidance for supported upgrade paths.
Treat exposed Rox sites as high priority until version status is confirmed.
Validation and detection
Inventory any BeWelcome Rox deployments and forks.
Compare deployed code against commit c60bf04.
Inspect code paths handling formkit_memory_recovery and bwRemember for unsafe unserialize use.
Review application logs for suspicious requests involving affected parameters or cookies.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-502 · source CWE mapping
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.