A Cross Site Request Forgery (CSRF) vulnerability exists in Issabel issabel-pbx version 4.0.0-6, which allows a remote attacker to exploit the lack of proper CSRF protections to create new user accounts in the application by tricking an authenticated user into executing malicious requests.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for a Cross Site Request Forgery (CSRF) vulnerability (CVE-2023-34839) in Issabel PBX version 4.0.0-6. The exploit is implemented as a single HTML file ('CSRF Exploit.html') that, when opened in a browser by an authenticated admin user, automatically submits a POST request to the Issabel PBX admin interface to create a new user with administrator privileges. The README.md provides context, usage instructions, and references to the vulnerability. The exploit targets the web interface at '/index.php?menu=userlist&action=new' and demonstrates privilege escalation via CSRF. The repository is structured simply, with the exploit code in HTML/JavaScript and documentation in Markdown.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.