Skip to main content
VulnerabilityPublished Updated

CVE-2024-25529: RuvarOA · SQL Injection

Affects RuvarOASource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 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 48% 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 26 Oct 2026.

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 identification of all RuvarOA instances running versions 6.01 and 12.01 within the organization’s environment is critical.
  2. Apply vendor patches or updates as soon as they become available; monitor RuvarOA vendor communications closely.
  3. In the absence of official patches, implement strict input validation and sanitization on the 'id' parameter at the web application level to block malicious SQL payloads.
  4. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint.
  5. Restrict external access to the affected web application, limiting it to trusted internal networks or VPN users where possible.
  6. Conduct thorough logging and monitoring of database queries and web server logs to detect suspicious activities indicative of exploitation attempts.
  7. Educate IT and security teams about this vulnerability to ensure rapid incident response if exploitation is detected.
  8. Consider network segmentation to isolate critical systems running RuvarOA from broader enterprise networks to limit lateral movement in case of compromise.

Description

RuvarOA v6.01 and v12.01 were discovered to contain a SQL injection vulnerability via the id parameter at /WorkFlow/wf_office_file_history_show.aspx.

References

Community reviews

Loading reviews…