CVE-2026-133239 in OpnForm
Summary
by MITRE • 11/20/2026
OpnForm before 2.8.2 contains an improper authorization vulnerability that allows unauthenticated attackers to move other forms' shared assets by supplying their URLs in file upload fields. Attackers can submit a public form with another form's cover or logo URL, causing Storage::move() to relocate it into submissions and break that asset.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in OpnForm versions prior to 2.8.2 represents a critical failure in access control mechanisms within the application's file handling subsystem. This improper authorization flaw specifically affects the functionality associated with shared assets, such as cover images or logos, which are intended to be accessible across multiple forms but remain protected against unauthorized modification by other users. The core technical issue lies in how the backend processes requests for moving these shared resources during form submission operations. When a user submits a public form that includes file upload fields designated for customizing appearance elements like covers or logos, the application accepts URLs provided by the attacker as valid inputs. Instead of validating whether the requesting entity has administrative privileges over the target asset being referenced in those URLs, the system blindly trusts the input and proceeds to execute storage operations on it.
From a technical perspective, this vulnerability exploits the lack of server-side authorization checks when invoking the Storage::move() method. The application logic assumes that if an attacker provides a URL pointing to another form's shared asset, they have legitimate rights to manipulate that resource. Consequently, by supplying the direct URL of a victim organization or user’s cover image or logo within their own public form submission, the attacker triggers the server-side relocation process. This action physically moves the file from its original directory structure into the submissions folder associated with the attacker's data. The result is not merely visual defacement but a functional disruption where the targeted asset becomes inaccessible in its intended context because it has been relocated to an incorrect path that does not align with the application’s expected static resource locations.
The operational impact of this vulnerability extends beyond simple denial of service for the affected assets. It compromises data integrity and availability, as critical branding elements or visual identifiers are removed from their proper storage location without consent. For organizations relying on OpnForm to maintain consistent public-facing identities through shared logos and covers, this attack effectively breaks those integrations until manual intervention restores the files. Furthermore, because the vulnerability allows unauthenticated actors to perform these actions via publicly accessible forms, it poses a significant risk in multi-tenant environments or when dealing with sensitive institutional data where visual consistency is paramount for trust and recognition. The ability to arbitrarily move server-side resources also hints at potential broader implications if similar authorization gaps exist elsewhere in the file management system, potentially leading to more severe outcomes such as overwriting critical configuration files depending on underlying filesystem permissions.
This flaw aligns closely with CWE-284, which describes Improper Access Control, specifically highlighting failures where a user can access or modify resources belonging to another entity without proper verification of privileges. In terms of offensive security frameworks, this behavior maps to the ATT&CK technique T1565.002, known as Stored Data Manipulation via Transferred Files. The attacker leverages stored data (the form submission) to execute a transfer that results in unauthorized modification of system resources. Mitigation strategies must focus on implementing strict server-side validation for all file operations involving shared assets. Developers should ensure that any request to move or modify a shared resource verifies the requester’s ownership or administrative rights over that specific asset ID before executing storage commands. Additionally, employing allowlists for permitted domains in URL-based uploads and sanitizing inputs can prevent indirect reference attacks. Upgrading to version 2.8.2 or later is essential as it addresses these authorization gaps by enforcing proper checks during the file movement process, ensuring that only authorized users can manipulate shared assets within their designated contexts.