CVE-2024-50919: jpress · n/a
Affects jpressSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjpressprojects/jpresspkg:github/jpressprojects/jpressOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement the following specific mitigations: 1) Restrict file upload functionality by enforcing strict server-side validation of file types, disallowing any executable or script file extensions such as .jsp. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious file uploads and command execution attempts. 3) Isolate the Jpress application in a sandboxed environment or container to limit the impact of potential exploitation. 4) Disable or restrict execution permissions on directories used for file uploads to prevent execution of uploaded files. 5) Monitor server logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected .jsp requests or command execution patterns. 6) Conduct regular security audits and vulnerability scans focusing on file upload mechanisms. 7) Prepare for rapid patch deployment once an official fix becomes available by maintaining an up-to-date inventory of affected systems. 8) Educate development and operations teams about secure file handling practices to prevent similar vulnerabilities in the future.
Description
Jpress until v5.1.1 has arbitrary file uploads on the windows platform, and the construction of non-standard file formats such as .jsp.can lead to arbitrary command execution