dbcve.org
NetmriApplication · Infoblox

CVE-2025-32814

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-22
Fix available
A fix is available. Upgrade to 7.6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue was discovered in Infoblox NETMRI before 7.6.1. Unauthenticated SQL Injection can occur.

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

Unauthenticated SQL injection in Infoblox NETMRI before version 7.6.1 allows remote attackers to inject arbitrary SQL queries without authentication, potentially enabling data exfiltration, privilege escalation, or complete database compromise.

MitigationUpgrade Infoblox NETMRI to version 7.6.1 or later to remediate the SQL injection vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NetmriApplication
Affected:< 7.6.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Infoblox NETMRI installation
    Locate NETMRI by checking for the application in the system. Common installation paths include /opt/netmri or check for the netmri service/process. On Linux, run: ps aux | grep -i netmri or ls -la /opt/ | grep -i netmri
    Affected if NETMRI is installed on the system
  2. Determine installed NETMRI version
    Check the version file or use the CLI. Common locations: /opt/netmri/version, /opt/netmri/lib/version.rb, or run: /opt/netmri/bin/netmri version. Alternatively, check the web interface login page for version information or examine /opt/netmri/VERSION file
    Affected if The installed version is lower than 7.6.1
  3. Verify management interface exposure
    Determine if the NETMRI web management interface (typically ports 80, 443, or 8080) is accessible from untrusted networks. Run: netstat -tlnp | grep -E '80|443|8080' or check firewall rules: iptables -L -n | grep -E '80|443|8080'
    Affected if The NETMRI management port is open to untrusted/external networks without proper network segmentation
  4. Check for SQL injection indicators
    Review web server logs for suspicious SQL injection patterns. Check /var/log/httpd/access_log or /opt/netmri/logs/* for entries containing SQL keywords like UNION, SELECT, INSERT, DROP, or common injection payloads. Run: grep -iE "(union|select|insert|drop|delete|update|1=1|' OR ')" /opt/netmri/logs/* 2>/dev/null
    Affected if Anomalous SQL-related patterns appear in logs, especially from unauthenticated requests
  5. Confirm vulnerability applicability
    The vulnerability is exploitable without authentication. Verify the web interface allows unauthenticated access to vulnerable endpoints. Check if the default login page or API endpoints are reachable without credentials and accept user input that could be exploited for SQL injection
    Affected if The web interface accepts unauthenticated requests with user-supplied input that could be passed to database queries

The system is affected if Infoblox NETMRI is installed with a version lower than 7.6.1 and the management interface is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 7.6.1 or later
Fixed in 7.6.1
Interim mitigation

Upgrade Infoblox NETMRI to version 7.6.1 or later to remediate the SQL injection vulnerability.

Recommended fix Moderate confidence

NetMRI 7.6.1 or later

  1. 1. Backup the current NetMRI configuration and database before proceeding with any upgrade.
  2. 2. Obtain the NetMRI version 7.6.1 (or later) from the Infoblox support portal at support.infoblox.com.
  3. 3. Follow the standard NetMRI upgrade procedure documented in the Infoblox NETMRI Upgrade Guide.
  4. 4. After upgrade, verify the NetMRI web interface is accessible and all services are running.
  5. 5. Confirm the SQL injection vulnerability is resolved by verifying version 7.6.1 is installed (typically found in Help > About or System > Diagnostics).

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netmri Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32814 — 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-2025-32814 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