CVE-2024-44838: rapidcms · SQL Injection
Affects rapidcmsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% 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 6 Sep 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopenrapid/rapidcmspkg:github/openrapid/rapidcmsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-44838, organizations should immediately implement the following measures: 1) Apply any official patches or updates from RapidCMS as soon as they become available. 2) In the absence of a patch, perform manual code review and sanitize the username parameter in /resource/runlogin.php to ensure proper input validation and use of parameterized queries or prepared statements to prevent SQL injection. 3) Deploy Web Application Firewalls (WAFs) with rules specifically targeting SQL injection patterns to block malicious requests. 4) Conduct thorough security testing, including automated vulnerability scans and manual penetration testing focused on SQL injection vectors. 5) Monitor database logs and web server logs for unusual queries or repeated failed login attempts indicative of exploitation attempts. 6) Restrict database user permissions to the minimum necessary to limit the impact of a potential compromise. 7) Educate developers and administrators about secure coding practices and the importance of input validation. 8) Consider isolating the CMS environment and implementing network segmentation to reduce lateral movement risks.
Description
RapidCMS v1.3.1 was discovered to contain a SQL injection vulnerability via the username parameter at /resource/runlogin.php.