Skip to main content
VulnerabilityPublished Updated

CVE-2026-30711: Devome GRR · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Mar 2026

  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

AI-suggested

  1. Immediately restrict access to Devome GRR instances to trusted networks and users only, minimizing exposure.
  2. Implement strict input validation and sanitization for HTTP headers, especially referer and user-agent, at the application or web server level as a temporary control.
  3. Monitor logs for unusual or malformed referer and user-agent header values that could indicate exploitation attempts.
  4. Enforce the principle of least privilege for all authenticated users to limit potential damage from exploitation.
  5. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting these headers.
  6. Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.
  7. Conduct regular security assessments and penetration tests focusing on authenticated attack vectors.
  8. Educate administrators and users about the risks of SQL injection and the importance of secure coding and configuration practices.
  9. Consider isolating forensic tools like Devome GRR from other critical infrastructure to contain potential compromises.

Description

Devome GRR v4.5.0 was discovered to contain multiple authenticated SQL injection vulnerabilities in the include/session.inc.php file via the referer and user-agent.

References

Community reviews

Loading reviews…