Database vendor-name disclosure via service-request SQL injection
Published Jul 16, 2025 · Updated Jul 18, 2025
SQL injection in HPE Telco Service Orchestrator before 5.2.1 allows remote authenticated users to query its database via service requests. HPE identifies service-request processing as the injection path but has not disclosed the affected endpoint, parameter, or query construction. Exploitation requires authenticated client access from an adjacent network; the only specifically documented consequence is disclosure of the database vendor name.
Summary
What happened
SQL injection in HPE Telco Service Orchestrator before 5.2.1 allows remote authenticated users to query its database via service requests. HPE identifies service-request processing as the injection path but has not disclosed the affected endpoint, parameter, or query construction. Exploitation requires authenticated client access from an adjacent network; the only specifically documented consequence is disclosure of the database vendor name.
The record
- CVE
- CVE-2025-37104
- Published
- Jul 16, 2025
- Updated
- Jul 18, 2025
- Vendor
- Hewlett Packard Enterprise (HPE)
- Product
- HPE Telco Service Orchestrator
- Classifications
- CWE-89
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 16, 2025CVE publishedPublication date reported by the CVE source.
- Jul 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo