Loading vulnerability…
CVE-2026-41472 is a stored cross-site scripting vulnerability in CyberPanel prior to version 2.4.5 affecting the AI Scanner workflow. The POST /api/ai-scanner/callback endpoint does not enforce authentication and accepts attacker-controlled scan result data that is written into ScanHistory records, including the findings_json field, without proper sanitization or output escaping. By submitting crafted content, an unauthenticated attacker can persist malicious JavaScript in AI Scanner results. When an authenticated administrator later opens the AI Scanner dashboard or results view, the injected script executes in the context of the CyberPanel origin and the administrator’s active session. In demonstrated exploitation, this browser-side execution was used to issue same-origin administrative actions and form part of a broader compromise chain leading to server-side command execution.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small standalone exploit for CVE-2026-41472 targeting CyberPanel <= 2.4.3. It contains two files: a README describing the vulnerability chain and a single Python exploit script. The exploit is not part of a larger framework. The main capability is a chained web attack: it sends an unauthenticated POST request to the CyberPanel AI Scanner callback endpoint (/api/ai-scanner/callback) with crafted JSON data. Inside the finding title, it embeds a stored XSS payload using an <img onerror> handler. When a CyberPanel administrator later views the poisoned AI Scanner page, the JavaScript executes in the admin browser, extracts the csrftoken from document.cookie, calls /websites/fetchWebsitesList to obtain a domain, and then submits a forged POST to /websites/addNewCron to create a cron job. That cron job runs a base64-decoded bash reverse shell to an attacker-supplied IP and port, resulting in server-side remote code execution. Repository structure is minimal and purpose-built: README.md documents the vulnerability chain, affected versions, and disclosure timeline; exploit.py implements the full attack flow. The Python code uses requests with TLS verification disabled, hardcoded placeholders for target URL and attacker callback details, and a fixed scan_id string. The exploit is operational rather than just demonstrative because it includes a working payload path to RCE, though customization is manual via placeholder replacement.
Repository contains a minimal two-file exploit: a README describing the vulnerability chain and a single Python script implementing the attack. The exploit targets CyberPanel <= 2.4.3 and chains an unauthenticated POST to /api/ai-scanner/callback with a stored XSS payload embedded in the finding title. The injected JavaScript executes when an administrator views the AI Scanner interface, extracts the csrftoken from document.cookie, calls /websites/fetchWebsitesList to obtain a domain, and then calls /websites/addNewCron to create a cron job. That cron job runs a base64-decoded bash reverse shell to ATTACKER_IP:ATTACKER_PORT. The script disables TLS verification warnings, uses hardcoded placeholders for target and callback values, and prints the cron command plus HTTP response details. Overall, this is a real exploit rather than a detector: it provides end-to-end stored XSS to authenticated admin action abuse and resulting remote code execution via cron persistence/execution.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.