CVE-2024-25531: RuvarOA · SQL Injection
Affects RuvarOASource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 11:42 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubruvaroa/RuvarOApkg:github/ruvaroa/RuvarOAOther 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-25531, organizations should immediately apply any available patches or updates from the RuvarOA vendor once released. In the absence of patches, implement strict input validation and sanitization on the PageID parameter to block malicious SQL payloads. Deploy Web Application Firewalls (WAFs) with rules targeting SQL injection patterns, specifically monitoring requests to /WebUtility/SearchCondiction.aspx. Conduct thorough code reviews and security testing of the affected modules to identify and remediate injection points. Restrict database permissions to the minimum necessary to limit the impact of potential injection attacks. Monitor database logs and application logs for unusual queries or errors indicative of exploitation attempts. Educate developers and administrators about secure coding practices and the risks of SQL injection. Finally, consider network segmentation to isolate critical systems and reduce attack surface exposure.
Description
RuvarOA v6.01 and v12.01 were discovered to contain a SQL injection vulnerability via the PageID parameter at /WebUtility/SearchCondiction.aspx.