CVE-2026-133239 json
OpnForm before 2.8.2 Unauthorized Asset Move via StoreFormSubmissionJob::storeFile
published 11h ago modified 8h ago also EUVD-2026-130317
- cvss
- 6.9
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- OpnForm OpnForm 2.8.2
- github.com/OpnForm/OpnForm@a1f6484 commit
- github.com/OpnForm/OpnForm#1370 pull request
- github.com/OpnForm/OpnForm/releases/tag/v2.8.2 release
Is CVE-2026-133239 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
Affected products
- OpnForm OpnForm
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/OpnForm/OpnForm/pull/1370
issue-tracking, patch
-
github.com
/OpnForm/OpnForm/commit/a1f64848ac261ed3df215855ffa297520a2ef35a
patch
-
github.com
/OpnForm/OpnForm/releases/tag/v2.8.2
release-notes
-
github.com
/OpnForm/OpnForm/blob/v2.8.1/api/app/Jobs/Form/StoreFormSubmissionJob.php#L407-L428
technical-description
-
github.com
/OpnForm/OpnForm
product
-
vulncheck.com
/advisories/opnform-before-2.8.2-unauthorized-asset-move-via-storeformsubmissionjob-storefile
third-party-advisory
Sources
- CVE List CVE-2026-133239
- NVD CVE-2026-133239
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.