CVE-2024-0986 is a medium severity OS command injection flaw, scored 4.7, in Issabel PBX 4.0.0. The public record names no fixed version and says the vendor did not respond. Restrict network access to the product, check your installed version against the one named in the record, and watch the vendor or project page for a patch.
What's affected
Affected: Issabel PBX 4.0.0. The record's CVSS 3.1 score is 4.7 (medium), with vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L. The record names the Asterisk-Cli component, reached through /index.php?menu=asterisk_cli, and the Command argument. The weakness is filed as CWE-78.
Fixed version: The record names no fixed version, and it notes that the vendor was contacted early and did not respond. No patched release is confirmed.
The record's kev flag is false, so this CVE is not in the CISA Known Exploited Vulnerabilities catalog. One thing to note: the VulDB wording in the description calls the issue critical, while the CVSS score in the record is 4.7, which is medium. Treat the numeric score and your own exposure as the guide, and know that both labels exist.
How to check if you're exposed
- Confirm the installed Issabel PBX version in the web interface or package list. The record lists 4.0.0.
- Check which networks and users can reach the web interface, and who holds administrator accounts.
- Look for the vulnerable page in your web server access logs and for unexpected child processes spawned by the web service account. Review who holds administrator logins and when they last signed in.
What to do now
- Take the product off the internet if it is exposed. Put it behind a VPN or an allow list of known addresses.
- Restrict access at the network layer to the people and systems that need it.
- Watch the vendor or project page for a fixed release, and apply it when one appears. The record says the vendor did not respond to disclosure, so do not wait on it: plan to replace the product if it handles sensitive data.
- Review logs for the signs above and rotate administrator credentials if you see anything unusual.
- Add the product to your inventory and monitoring so a future fix or advisory reaches you. A free in-browser dependency scan covers the third party packages in software you build, though it does not inspect device firmware.
Why it matters
OS command injection happens when input from a user ends up inside a command that the server hands to the operating system. If the input is not neutralized, the person supplying it can add their own commands to the one the developer intended. The commands run with the privileges of the web service, which on an appliance such as a PBX is often high.
The CVSS vector requires high privileges, so an attacker needs an administrator style login first. That lowers the score, but it does not make the bug harmless. Admin credentials are phished, reused and guessed often enough that a post authentication command injection is a real step from web access to full control of the host.
The record states that the exploit has been disclosed to the public. That means details are available to others, not that attacks have been observed. Only CISA KEV or a vendor advisory can say that, and neither does here.
Quick check
Is this CVE exploited in the wild?
The record's kev flag is false, so it is not in the CISA Known Exploited Vulnerabilities catalog, and no source I read reports active exploitation. The record does say a public exploit exists. That is a reason to patch or contain it soon, not a report of attacks.
What if there is no patch?
Reduce exposure. Remove internet access, restrict the network, apply the log and credential checks above, and plan to replace the product if it holds sensitive data.
Sources
- Safeguard Gold entry for CVE-2024-0986, built from the NVD record
- NVD record fields: description, CVSS 3.1 vector, CWE list and CPE product data. I did not fetch the researcher write ups listed in the record, so the details above are limited to what the record states.
Last reviewed: 19 October 2026.
