CVE-2024-28623: ritecms · n/a
Affects ritecmsSource CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 13 Mar 2024
Detectable: evidence found.
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by mitre
, 5 days before disclosure
CVE published
on cve.org
, t = 0
First Exploit-DB entry (opens in a new tab)
RiteCMS 3.0.0 - Reflected Cross Site Scripting (XSS)
, 1.4 years after disclosure
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 |
|---|---|---|
GitHubgurjotexpert/ritecmspkg:github/gurjotexpert/ritecmsOther 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-28623, organizations should implement strict input validation and output encoding on all user-supplied data within the main_menu/edit_section component to neutralize malicious scripts. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Disable or restrict the ability to input HTML or JavaScript in editable sections until an official patch is available. Monitor web application logs for suspicious input patterns or repeated attempts to exploit XSS. Educate users and administrators about the risks of clicking unknown links or interacting with untrusted content. If possible, isolate the affected component behind additional authentication or network controls to reduce exposure. Regularly check for updates from RiteCMS developers and apply patches promptly once released. Consider deploying web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting this vulnerability. Finally, conduct security testing and code reviews focused on input handling in the affected component to identify and remediate similar issues proactively.
Description
RiteCMS v3.0.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the component main_menu/edit_section.