# CVE-2025-37104: HPE Telco Service Orchestrator Software, Authenticated SQL Injection

> Authenticated attackers can perform SQL injection to exfiltrate database vendor names from HPE Telco Service Orchestrator.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2025
- **Updated:** 18 Jul 2025
- **Also known as:** GHSA-jpfc-4529-pj3r

## What is CVE-2025-37104?

CVE-2025-37104 is a high-severity SQL injection vulnerability in Hewlett Packard Enterprise (HPE) HPE Telco Service Orchestrator, published on 16 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been identified in HPE Telco Service Orchestrator software. The vulnerability could allow authenticated clients to to perform a SQL Injection attack when sending a service request, and potentially exfiltrate the database's vendor name to unauthorized authenticated clients.

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

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


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

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

## Is CVE-2025-37104 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-37104 is a high-severity SQL injection vulnerability in Hewlett Packard Enterprise (HPE) HPE Telco Service Orchestrator, published on 16 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-37104 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) HPE Telco Service Orchestrator. 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-37104/ (Markdown: https://insights.sbomify.com/CVE-2025-37104/index.md)
```

## Sources

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

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