CVE-2024-48177: 123 · SQL Injection
Affects 123Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 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 |
|---|---|---|
GitHubdabaizhizhu/123pkg:github/dabaizhizhu/123Other 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-48177, organizations should immediately restrict access to the /admin/article/delete.do endpoint to trusted administrators only, employing network-level controls such as IP whitelisting or VPN access. Implement strict input validation and parameterized queries or prepared statements to sanitize the RID parameter and prevent SQL injection. If a patch becomes available from MRCMS developers, apply it promptly. In the absence of an official patch, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the RID parameter. Conduct thorough audits of user privileges to ensure minimal necessary access is granted, reducing the risk of exploitation by low-privilege users. Regularly monitor logs for suspicious database queries or unusual activity related to the vulnerable endpoint. Additionally, perform database backups and test recovery procedures to minimize impact in case of data compromise or loss.
Description
MRCMS 3.1.2 contains a SQL injection vulnerability via the RID parameter in /admin/article/delete.do.