CVE-2024-44839: rapidcms · n/a
Affects rapidcmsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 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-25.
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-44839, organizations should first check for any official patches or updates from RapidCMS developers and apply them immediately once available. In the absence of a patch, administrators should implement input validation and sanitization on the articleid parameter to block malicious SQL payloads. Employing a Web Application Firewall (WAF) with rules targeting SQL injection patterns can provide temporary protection. Restrict database user privileges to the minimum necessary to limit the impact of a potential injection. Regularly audit and monitor database queries and logs for suspicious activity. Additionally, consider isolating the CMS environment and backing up data frequently to enable quick recovery. Educating developers and administrators on secure coding practices and conducting security assessments on web applications can prevent similar vulnerabilities in the future.
Description
RapidCMS v1.3.1 was discovered to contain a SQL injection vulnerability via the articleid parameter at /default/article.php.