CVE-2024-25519: RuvarOA · SQL Injection
Affects RuvarOASource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% 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
- Immediate mitigation should focus on restricting access to the vulnerable endpoint (/WorkFlow/wf_work_print.aspx) via network segmentation or firewall rules to limit exposure.
- Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the idlist parameter.
- Apply strict input validation and parameterized queries or stored procedures in the application code to prevent injection attacks once patches become available.
- Monitor database logs and application logs for unusual queries or error messages indicative of injection attempts.
- Conduct a thorough security audit of the RuvarOA deployment to identify and remediate other potential injection points.
- Engage with the vendor or community to obtain official patches or updates as soon as they are released.
- Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases.
- Consider deploying runtime application self-protection (RASP) solutions to detect and block injection attacks in real time.
Description
RuvarOA v6.01 and v12.01 were discovered to contain a SQL injection vulnerability via the idlist parameter at /WorkFlow/wf_work_print.aspx.