CVE-2026-33133 affects WeGIA, a web manager for charitable institutions. In WeGIA versions 3.6.5 and 3.6.6, the loadBackupDB() function imports SQL files from uploaded backup archives without validating the SQL content before execution. Because backup archives are trusted implicitly, a privileged attacker can supply a crafted backup containing arbitrary SQL statements. This allows direct execution of attacker-controlled database commands during the restore/import process, including creation of rogue administrator accounts, modification of existing passwords, and other unauthorized database changes. The vulnerable behavior was introduced in commit 370104c and patched in version 3.6.7.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
4 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.