CVE-2025-30004 json
Xorcom CompletePBX <= 5.2.35 Task Scheduler Authenticated Command Injection
published last yr. modified 4mo ago also EUVD-2025-8863
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.3%
- EPSS 4.3% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Metasploit
Summary
Xorcom CompletePBX is vulnerable to command injection in the administrator Task Scheduler functionality, allowing for attackers to execute arbitrary commands as the root user.
This issue affects CompletePBX: all versions up to and prior to 5.2.35
Patch / fix
- xorcom completepbx 5.2.36.1
Is CVE-2025-30004 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/linux/http/xorcom_completepbx_scheduler)
- Published
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
4.31% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/linux/http/xorcom_completepbx_scheduler Xorcom CompletePBX Authenticated Command Injection via Task Scheduler metasploit exploit, excellent rank, 2025-03-02
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 |
Affected products
- Xorcom CompletePBX
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
xorcom.com
/new-completepbx-release-5-2-36-1/
vendor-advisory, release-notes
-
vulncheck.com
/advisories/completepbx-authenticated-command-injection
third-party-advisory
Sources
- CVE List CVE-2025-30004
- NVD CVE-2025-30004
Fencer Intel 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.