CVE-2024-28393: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
AI-suggested
Organizations should immediately assess their use of Scalapay and identify if they are running version 1.2.41 or earlier. Since no official patches are currently available, temporary mitigations include implementing strict input validation and sanitization on all user inputs processed by the ScalapayReturnModuleFrontController. Deploying a web application firewall (WAF) with rules specifically designed to detect and block SQL injection attempts targeting Scalapay endpoints can reduce risk. Monitoring database logs and application logs for unusual queries or errors related to SQL injection attempts is critical for early detection. Segmentation of the database and limiting database user privileges can minimize the impact if exploitation occurs. Organizations should maintain close communication with Scalapay vendors for timely patch releases and apply updates as soon as they become available. Additionally, conducting penetration testing focused on SQL injection vectors in the affected modules can help identify residual risks.
Description
SQL injection vulnerability in scalapay v.1.2.41 and before allows a remote attacker to escalate privileges via the ScalapayReturnModuleFrontController::postProcess() method.