Loading vulnerability…
A SQL injection vulnerability exists in Sequelize, a Node.js ORM, prior to version 6.19.1. The vulnerability arises when user-supplied parameters are passed through the 'replacements' option and are not properly escaped, allowing attackers to inject arbitrary SQL code. This is particularly exploitable when 'replacements' and the 'where' option are used together in a query.
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 is a proof-of-concept (PoC) exploit for CVE-2023-25813, a critical SQL injection vulnerability in Sequelize ORM versions prior to 6.19.1. The exploit demonstrates how improper handling of the 'replacements' option in Sequelize queries can allow attackers to inject arbitrary SQL, even when using parameterized queries. The repository includes a Node.js Express application with user registration, login, and search endpoints. The vulnerable code is in 'index.js', where user-supplied input is passed to Sequelize's 'literal' and 'replacements' options in a way that allows SQL injection. The configuration file 'config/config.json' sets up a MySQL database on localhost with 'multipleStatements' enabled, which is necessary for exploiting the vulnerability to execute multiple SQL statements (e.g., dropping tables). The main attack vector is via HTTP POST requests to '/login' and '/search', where crafted input can result in arbitrary SQL execution. The repository structure is typical for a Node.js web application, with models for user data, configuration files, and static HTML for the frontend. The exploit is operational as a PoC and does not include weaponized or automated payload delivery, but clearly demonstrates the risk and impact of the 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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.