Skip to main content
CVE-2024-25519VulnerabilityPublished Updated

CVE-2024-25519: RuvarOA · n/a

Affects RuvarOASource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubruvaroa/RuvarOApkg:github/ruvaroa/RuvarOAOther threatsAffected
  • =6.01
  • =12.01
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. 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. 2. Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the idlist parameter. 3. Apply strict input validation and parameterized queries or stored procedures in the application code to prevent injection attacks once patches become available. 4. Monitor database logs and application logs for unusual queries or error messages indicative of injection attempts. 5. Conduct a thorough security audit of the RuvarOA deployment to identify and remediate other potential injection points. 6. Engage with the vendor or community to obtain official patches or updates as soon as they are released. 7. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases. 8. 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.

References

Community reviews

Loading reviews…