Skip to main content
CVE-2024-25508VulnerabilityPublished Updated

CVE-2024-25508: ruvaroa · n/a

Affects ruvaroaSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 08:11 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
NuGetruvaroapkg:nuget/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

Given the absence of official patches, organizations should implement immediate compensating controls. These include deploying web application firewalls (WAFs) with rules specifically targeting SQL injection attempts on the /bulletin/bulletin_template_show.aspx endpoint and the 'id' parameter. Input validation and sanitization should be enforced at the application level if source code access is available, employing parameterized queries or stored procedures to prevent injection. Network segmentation and strict access controls can limit exposure of the vulnerable application. Continuous monitoring and logging of database queries and web requests should be enhanced to detect suspicious activity early. Organizations should also engage with RuvarOA vendors or support channels to obtain patches or updates and plan for timely application once available. Regular security assessments and penetration testing focusing on injection flaws are recommended to validate defenses.

Description

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

References

Community reviews

Loading reviews…