Skip to main content
VulnerabilityPublished Updated

CVE-2024-48465: The MRBS version 1.5.0 has an SQL injection

Affects mrbsSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Debiandebian/mrbspkg:deb/debian/mrbsOther threatsAffected
  • =1.5.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately restrict external access to MRBS 1.5.0 instances by network segmentation or firewall rules to limit exposure.
  2. Monitor web server logs for suspicious requests targeting edit_entry_handler.php and the rooms[] parameter to detect potential exploitation attempts.
  3. Implement a Web Application Firewall (WAF) with SQL injection detection and prevention rules tailored to block malicious payloads targeting MRBS.
  4. Review and sanitize all user inputs in the application code, especially the rooms[] parameter, to prevent SQL injection; if possible, apply prepared statements or parameterized queries.
  5. Engage with MRBS maintainers or community to obtain or request an official patch or upgrade to a fixed version once available.
  6. Conduct regular vulnerability scans and penetration tests focusing on web application security to identify similar injection flaws.
  7. Educate system administrators and developers about secure coding practices and the risks of SQL injection vulnerabilities.
  8. Maintain up-to-date backups of MRBS databases to enable recovery in case of data compromise or destruction.

Description

The MRBS version 1.5.0 has an SQL injection vulnerability in the edit_entry_handler.php file, specifically in the rooms%5B%5D parameter

References

Community reviews

Loading reviews…