dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-30711

HIGH · 8.8 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated SQL injection vulnerabilities exist in Devome GRR v4.5.0 within include/session.inc.php where the referer and user-agent HTTP header values are directly used in SQL queries without proper sanitization or parameterization, allowing an authenticated attacker to manipulate SQL queries.

MitigationImplement prepared statements/parameterized queries for all SQL operations involving referer and user-agent headers, or upgrade to a patched version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Devome GRR installation directory
    Search for the GRR application files, typically found in web server document roots under a 'grr' or 'GRR' folder. Check common paths like /var/www/html/grr, /www/grr, or search for 'session.inc.php' which is part of the GRR codebase.
    Affected if The file include/session.inc.php exists within the web application's directory structure.
  2. Identify installed GRR version
    Check the version file or header within the GRR installation. Look for a version.php, version.inc.php, or check the main index.php for a version string. Common locations include grr/version.php or grr/include/version.inc.
    Affected if The installed version is 4.5.0 or falls within an unpatched version range that retains the vulnerable session.inc.php code.
  3. Verify the vulnerable code pattern in session.inc.php
    Examine the file include/session.inc.php and search for direct usage of $_SERVER['HTTP_REFERER'] or $_SERVER['HTTP_USER_AGENT'] within SQL query strings without proper escaping, parameterization, or use of prepared statements.
    Affected if The file contains SQL queries that directly incorporate $_SERVER['HTTP_REFERER'] or $_SERVER['HTTP_USER_AGENT'] variables without sanitization functions.
  4. Confirm database connectivity is in use
    Check if GRR is configured to use a database by examining config files like include/config.inc.php or config/database.php for database connection parameters (dbType, dbHost, dbUser, dbPass, dbName).
    Affected if The application is configured with database credentials and connects to a MySQL, PostgreSQL, or SQLite database.
  5. Check if authentication is enabled
    Review the GRR configuration to determine whether user authentication is required and functional. Look for session management files and authentication-related settings in the config files.
    Affected if User authentication is enabled and functional in the GRR installation, allowing an attacker to obtain valid credentials for the SQL injection attack.

A user is affected if they are running Devome GRR version 4.5.0 (or an unpatched version) with the vulnerable include/session.inc.php file containing unsanitized $_SERVER['HTTP_REFERER'] or $_SERVER['HTTP_USER_AGENT'] in SQL queries, connected to a database with authentication enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all SQL operations involving referer and user-agent headers, or upgrade to a patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30711 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data