# CVE-2025-32813: An issue was discovered in Infoblox NETMRI before 7.6.1.


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-9888-65w8-vw6m

## What is CVE-2025-32813?

CVE-2025-32813 is a high-severity vulnerability in n/a, published on 22 May 2025. 

### Official description

An issue was discovered in Infoblox NETMRI before 7.6.1. Remote Unauthenticated Command Injection can occur.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-32813?

It affects 1 product.


Products: Infoblox Netmri.

## How do I fix CVE-2025-32813?

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

## Is CVE-2025-32813 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32813 exists.

Public exploit code:

- Infoblox NetMRI < 7.6.1 - Unauthenticated Command Injection in get_saml_request (nuclei): http/cves/2025/CVE-2025-32813.yaml

## Other vulnerabilities in n/a

- [CVE-2015-2033](https://insights.sbomify.com/CVE-2015-2033/): Auth bypass in n/a (critical 10.0)
- [CVE-2014-3418](https://insights.sbomify.com/CVE-2014-3418/): Command injection in n/a (critical 10.0)
- [CVE-2025-32814](https://insights.sbomify.com/CVE-2025-32814/): SQL injection in n/a (critical 9.8)
- [CVE-2024-52874](https://insights.sbomify.com/CVE-2024-52874/): SQL injection in n/a (high 8.8)
- [CVE-2014-3419](https://insights.sbomify.com/CVE-2014-3419/): Hardcoded credentials in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32813 and fix it if it is affected.

What it is: CVE-2025-32813 is a high-severity vulnerability in n/a, published on 22 May 2025. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32813 exists.

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-2025-32813/ (Markdown: https://insights.sbomify.com/CVE-2025-32813/index.md)
```

## Sources

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

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