Loading vulnerability…
CVE-2024-54761 is a SQL injection vulnerability in BigAnt Office Messenger version 5.6.06. According to the provided content, the issue is reachable via the 'dev_code' parameter. Insufficient neutralization of attacker-controlled input in this parameter allows crafted SQL syntax to be injected into backend database queries. No additional information about the specific endpoint, code path, or vulnerable function was provided in the available content.
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 (1 hidden).
This repository contains a Python exploit script (CVE-2024-54761.py) and a README for CVE-2024-54761, a critical SQL injection vulnerability in BigAnt Office Messenger 5.6.06. The exploit targets the web interface (default port 8000) and automates the following steps: (1) authenticates to the application (default credentials: admin/123456), (2) exploits a SQL injection vulnerability in the 'dev_code' parameter of a specific endpoint to write a PHP webshell to the server's webroot, and (3) provides an interactive shell for executing arbitrary commands via the webshell. The script is operational and provides a working payload (PHP webshell), requiring only the target's IP and (optionally) credentials. The README provides usage instructions, manual exploitation steps, and proof-of-concept screenshots. The exploit is network-based, requires access to the web interface, and is specific to Windows installations of BigAnt Office Messenger. No framework is used; the code is standalone Python.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.