# CVE-2025-54966: Information disclosure in n/a

> Attackers can access sensitive local file paths and version information via Job Status Service endpoints in SOCET GXP.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2025
- **Updated:** 24 Oct 2025
- **Also known as:** GHSA-7m2g-57pq-h3xr

## What is CVE-2025-54966?

CVE-2025-54966 is a medium-severity vulnerability in n/a, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in BAE SOCET GXP before 4.6.0.2. Some endpoints on the SOCET GXP Job Status Service may return sensitive information in certain situations, including local file paths and SOCET GXP version information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Baesystems Socet Gxp.

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

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

## Is CVE-2025-54966 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-54968](https://insights.sbomify.com/CVE-2025-54968/): Missing authorization in n/a (high 8.8)
- [CVE-2025-54964](https://insights.sbomify.com/CVE-2025-54964/): Command injection in n/a (high 8.4)
- [CVE-2025-54967](https://insights.sbomify.com/CVE-2025-54967/): XML external entity in n/a (medium 6.5)
- [CVE-2025-54970](https://insights.sbomify.com/CVE-2025-54970/): Missing authorization in n/a (medium 6.5)
- [CVE-2025-54963](https://insights.sbomify.com/CVE-2025-54963/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54966 is a medium-severity vulnerability in n/a, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54966 in the wild and no public exploit code.

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

## Sources

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

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