Skip to main content
VulnerabilityPublished Updated

CVE-2024-25510: 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 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 7 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 mitigation should include implementing web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting the 'id' parameter in /AddressBook/address_public_show.aspx.
  2. Employ input validation and sanitization on all user-supplied data, especially the 'id' parameter, using allowlists and rejecting suspicious characters.
  3. Use parameterized queries or prepared statements in the application code to prevent injection.
  4. Restrict database user permissions to the minimum necessary to limit damage in case of exploitation.
  5. Monitor logs for unusual database queries or errors indicative of injection attempts.
  6. Conduct a thorough code review and security audit of the affected modules.
  7. Engage with RuvarOA vendors or community for patches or official updates and apply them promptly once available.
  8. Consider isolating or segmenting systems running vulnerable versions to reduce exposure.
  9. Educate IT and security teams about this vulnerability to ensure rapid detection and response.
  10. If patching is delayed, consider temporary disabling or restricting access to the vulnerable endpoint if feasible.

Description

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

References

Community reviews

Loading reviews…