Skip to main content
VulnerabilityPublished Updated

CVE-2024-25520: RuvarOA · SQL Injection

Affects RuvarOASource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 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 49% 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

To mitigate CVE-2024-25520, organizations should immediately identify and inventory all RuvarOA instances, focusing on versions 6.01 and 12.01. Since no official patches are currently available, temporary mitigations include implementing strict input validation and sanitization on the 'id' parameter at the web application level. Deploying a Web Application Firewall (WAF) with rules to detect and block SQL injection patterns targeting the vulnerable endpoint can provide an effective barrier. Monitoring database logs and application logs for unusual queries or errors related to the 'id' parameter can help detect attempted exploitation. Restricting database user permissions to the minimum necessary can limit the impact of a successful injection. Organizations should also engage with RuvarOA vendors or security communities for updates on patches or official fixes and plan for prompt deployment once available. Regular security assessments and penetration testing focusing on SQL injection vectors are recommended to ensure ongoing protection.

Description

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

References

Community reviews

Loading reviews…