CVE-2022-26630: Jellycms v3.8.1 and below was discovered to contain an arbitrary file upload vulnerability via \app.\admin\Con
CVE-2022-26630 is a high-severity flaw (CVSS 8.8) affecting jellycms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Jellycms v3.8.1 and below was discovered to contain an arbitrary file upload vulnerability via \app.\admin\Controllers\db.php.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 1.0% (top 39%) |
| CISA exploited list | No |
| Weakness | CWE-434 |
| Published | 2022-04-05 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-26630?
jellycms: upgrade to newer than 3.8.1. Exact commands for each OS are on this page.
Is CVE-2022-26630 being exploited?
CVE-2022-26630 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-26630 affect?
CVE-2022-26630 affects jellycms. Severity is high (CVSS 8.8). Jellycms v3.8.1 and below was discovered to contain an arbitrary file upload vulnerability via \app.\admin\Controllers\db.php.
How urgent is CVE-2022-26630?
Priority 51/100. High severity; Public exploit reference