CVE-2024-25530: RuvarOA · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% 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
Given the absence of an official patch, organizations should immediately implement the following mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the PageID parameter and the specific vulnerable endpoint. 2) Conduct thorough input validation and sanitization on all user-supplied data, especially parameters passed to SQL queries, using parameterized queries or prepared statements if possible. 3) Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. 4) Monitor database logs and application logs for unusual queries or errors indicative of injection attempts. 5) Isolate the RuvarOA application server from critical network segments to limit lateral movement. 6) Consider temporary disabling or restricting access to the vulnerable endpoint if feasible. 7) Stay alert for vendor updates or patches and plan for immediate deployment once available. 8) Conduct security awareness training for administrators to recognize and respond to signs of exploitation.
Description
RuvarOA v6.01 and v12.01 were discovered to contain a SQL injection vulnerability via the PageID parameter at /WebUtility/get_find_condiction.aspx.