CVE-2025-50901: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% 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 20 Aug 2025
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
AI-suggested
Organizations should immediately audit their JeeWMS installations to identify if they are running the vulnerable version or builds derived from the specified commit. In the absence of an official patch, it is recommended to implement network-level protections such as restricting access to JeeWMS interfaces via firewalls or VPNs to trusted users only. Employing Web Application Firewalls (WAFs) with custom rules to detect and block anomalous requests targeting authentication mechanisms can reduce exposure. Monitoring logs for unusual access patterns or unauthorized file access attempts is critical for early detection. If possible, disable or isolate the vulnerable service until a vendor patch is released. Organizations should also engage with the vendor or community to obtain updates or mitigations and prepare for prompt patch deployment once available. Finally, reviewing and tightening file permissions on the server to limit the impact of arbitrary file reads can help contain potential damage.
Description
JeeWMS 771e4f5d0c01ffdeae1671be4cf102b73a3fe644 (2025-05-19) contains incorrect authentication bypass vulnerability, which can lead to arbitrary file reading.