# CVE-2025-27631: Other in TRMTracker

> An attacker can inject LDAP queries to execute remote commands and read or modify data in the TRMTracker web application.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-2jgf-qh2v-pfqg

## What is CVE-2025-27631?

CVE-2025-27631 is a medium-severity vulnerability in Hitachi Energy TRMTracker, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TRMTracker web application is vulnerable to LDAP injection attack potentially allowing an attacker to inject code into a query and execute remote commands that can read and update data on the website.

Weakness: CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query)

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


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

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

## Is CVE-2025-27631 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27631 is a medium-severity vulnerability in Hitachi Energy TRMTracker, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27631 in the wild and no public exploit code.

Affected product: Hitachi Energy TRMTracker. 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-27631/ (Markdown: https://insights.sbomify.com/CVE-2025-27631/index.md)
```

## Sources

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

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