CVE-2022-23626 json
Insufficient file checks in m1k1o/blog
published 2022-02-08 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-28584
- cvss
- 8.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.9%
- EPSS 9.9% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
m1k1o/blog is a lightweight self-hosted facebook-styled PHP blog. Errors from functions `imagecreatefrom*` and `image*` have not been checked properly. Although PHP issued warnings and the upload function returned `false`, the original file (that could contain a malicious payload) was kept on the disk. Users are advised to upgrade as soon as possible. There are no known workarounds for this issue.
Patch / fix
Timeline
- Published
- First public exploit (EDB-50943)
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
9.87% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-50943 m1k1o's Blog v.10 - Remote Code Execution (RCE) (Authenticated) webapps, 2022-05-23
- packetstormsecurity.com http://packetstormsecurity.com/files/167235/m1k1os-Blog-1.3-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- m1k1o blog
Classification
References
-
github.com
/m1k1o/blog/commit/6f5e59f1401c4a3cf2e518aa85b231ea14e8a2ef
patch, third-party-advisory
-
packetstormsecurity.com
/files/167235/m1k1os-Blog-1.3-Remote-Code-Execution.html
exploit, third-party-advisory, vdb-entry
-
github.com
/m1k1o/blog/security/advisories/GHSA-wmqj-5v54-24x4
third-party-advisory
Sources
- CVE List CVE-2022-23626
- NVD CVE-2022-23626
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.