CVE-2024-45771: rapidcms · n/a
Affects rapidcmsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% 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 2026-10-26.
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-45771, organizations should immediately assess their use of RapidCMS version 1.3.1 and restrict access to the /resource/runlogin.php endpoint where possible. Since no official patches are currently available, implement the following specific measures: 1) Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the password parameter; 2) Conduct input validation and sanitization on all user-supplied data, especially the password field, using allowlists and parameterized queries or prepared statements if modifying source code is feasible; 3) Monitor database logs and application logs for unusual queries or failed login attempts indicative of injection attempts; 4) Limit database user privileges associated with the CMS to the minimum necessary to reduce potential damage; 5) Isolate the CMS environment from critical internal networks to contain potential breaches; 6) Stay alert for official patches or updates from RapidCMS developers and apply them promptly once released; 7) Educate security teams about this vulnerability to ensure rapid detection and response to suspicious activity.
Description
RapidCMS v1.3.1 was discovered to contain a SQL injection vulnerability via the password parameter at /resource/runlogin.php.