FacturaScripts (open-source ERP/accounting) prior to 2025.81 contains a critical SQL injection in its REST API sorting implementation. User-controlled input from the sort parameter is passed into ModelClass::getOrderBy() and directly concatenated into the SQL ORDER BY clause without adequate validation/sanitization, enabling authenticated API users to inject arbitrary SQL via ORDER BY manipulation across API endpoints that support sorting. The issue is fixed in 2025.81.
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.
ORDER BY clause, potentially resulting in full database disclosure (e.g., credentials/API keys, PII, financial and configuration data) and potentially broader compromise depending on database permissions available to the application.If you can’t patch tonight, do this now.
sort[...] parameters at an API gateway/WAF or disable sorting where feasible; restrict API access to trusted networks/clients; rotate/minimize API tokens; and ensure the API uses a least-privilege database account to reduce the impact of successful SQL injection.Patch, then assume compromise.
ASC/DESC only; ensure ORDER BY identifiers are handled safely (e.g., escaped identifiers / query builder) and prevent raw SQL/function injection via crafted sort values.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
1 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.