CVE-2024-25532: RuvarOA · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% 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 8 May 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
AI-suggested
To mitigate CVE-2024-25532, organizations should immediately assess their use of RuvarOA versions 6.01 and 12.01 and prioritize upgrading to patched versions once available. In the absence of official patches, implement strict input validation and sanitization on the bt_id parameter to block malicious SQL payloads. Deploy Web Application Firewalls (WAFs) with rules specifically targeting SQL injection patterns, particularly on the /include/get_dict.aspx endpoint. Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts. Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. Network segmentation can help contain any breach resulting from exploitation. Additionally, conduct regular security assessments and penetration testing focused on injection vulnerabilities. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases. Maintain up-to-date backups to enable recovery in case of data corruption or deletion.
Description
RuvarOA v6.01 and v12.01 were discovered to contain a SQL injection vulnerability via the bt_id parameter at /include/get_dict.aspx.