CVE-2022-1811 json
Unrestricted Upload of File with Dangerous Type in publify/publify
published 2022-05-23 4 y ago modified 2026-06-17 4 mo ago also BIT-publify-2022-1811 , EUVD-2022-2196 , GHSA-3hwx-c6cp-q972
- cvss
- 9.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
Unrestricted Upload of File with Dangerous Type in GitHub repository publify/publify prior to 9.2.9.
Patch / fix
- rubygems publify_core 9.2.9
- bitnami publify 9.2.9
- publify publify/publify 9.2.9
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/4d97f665-c9f1-4c38-b774-692255a7c44c referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L |
| GitHub | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
| OSV | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | publify_core | <9.2.9 |
9.2.9 |
| bitnami | publify | <9.2.9 |
9.2.9 |
Affected products
- publify publify/publify
Classification
References
-
github.com
/publify/publify/commit/0fb6b027fbaf17f6a6551f2148482a03eac12927
web, patch, third-party-advisory
-
huntr.dev
/bounties/4d97f665-c9f1-4c38-b774-692255a7c44c
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-1811
advisory
-
github.com
/publify/publify
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/publify_core/CVE-2022-1811.yml
web
Sources
- CVE List CVE-2022-1811
- GitHub Advisory GHSA-3hwx-c6cp-q972
- NVD CVE-2022-1811
- OSV BIT-publify-2022-1811
Fencer Vulns 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.