Loading vulnerability…
Bacula-web versions before 9.7.1 contain an SQL injection vulnerability reachable through a crafted HTTP GET request. A remote attacker can exploit the flaw to execute arbitrary code.
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 CVE-2025-45346, a time-based blind SQL injection vulnerability in Bacula-Web's 'jobfiles' endpoint when using a PostgreSQL backend. The repository consists of a detailed README.md explaining the vulnerability, usage, and impact, and a Python script (cve-2025-45346.py) that automates the exploitation process. The script first verifies the presence of the SQL injection by measuring response delays when injecting a 'pg_sleep' function call. If successful, it proceeds to extract the PostgreSQL version string from the database, character by character, using time-based inference. The script requires the user to configure the target URL and a valid session cookie. The main attack vector is remote network access to the vulnerable HTTP endpoint. The exploit is a functional PoC, not weaponized, and does not provide post-exploitation capabilities beyond information disclosure (database version extraction).
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 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.