# CVE-2026-30711: SQL injection in n/a

> Authenticated attackers can execute SQL commands via referer and user-agent headers in Devome GRR, potentially reading or modifying database contents.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-c44j-rqvr-7mwv

## What is CVE-2026-30711?

CVE-2026-30711 is a high-severity SQL injection vulnerability in n/a, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-30711?


## How do I fix CVE-2026-30711?

No fix has been published for CVE-2026-30711 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-30711 being exploited?

There is no known exploitation of CVE-2026-30711 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30711 and fix it if it is affected.

What it is: CVE-2026-30711 is a high-severity SQL injection vulnerability in n/a, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30711 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30711/ (Markdown: https://insights.sbomify.com/CVE-2026-30711/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30711
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30711
- OSV: https://osv.dev/vulnerability/CVE-2026-30711

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30711/
Summaries are generated and may contain mistakes; the official description above is the record.