Skip to main content
CVE-2025-45854VulnerabilityPublished Updated

CVE-2025-45854: JEHC-BPM · Missing Authorization

Affects JEHC-BPMSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.1% chance of exploitation in 30 days – higher than 87% 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:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq 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-26.

What to do

Affected software

ProductAffectedFixed in
GitHubjehc/JEHC-BPMpkg:github/jehc/JEHC-BPMOther threatsAffected
  • =2.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate network-level protections: Restrict access to the /server/executeExec endpoint by implementing strict firewall rules and network segmentation to limit exposure only to trusted internal systems. 2. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting execParams or attempts to invoke code execution via this endpoint. 3. Monitor logs and network traffic for unusual activity related to the vulnerable endpoint, including unexpected parameter values or spikes in requests. 4. Disable or restrict the use of the /server/executeExec endpoint if possible, or apply application-level access controls to enforce strict authorization until an official patch is released. 5. Engage with the vendor JEHc for timely updates and patches; prioritize patching as soon as a fix becomes available. 6. Conduct thorough security assessments of the BPM environment to identify any signs of compromise or lateral movement. 7. Educate IT and security teams about this vulnerability to ensure rapid detection and response. 8. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation attempts targeting this vulnerability.

Description

/server/executeExec of JEHC-BPM 2.0.1 allows attackers to execute arbitrary code via execParams.

References

Community reviews

Loading reviews…