# CVE-2025-4527: Dígitro NGC Explorer Password Transmission client-side enforcement of server-side security

> Attackers can bypass client-side security checks in Dígitro NGC Explorer, potentially circumventing intended server-side protections.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2025
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-2h27-gcg3-7h2g

## What is CVE-2025-4527?

CVE-2025-4527 is a medium-severity vulnerability in Dígitro NGC Explorer, published on 11 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in Dígitro NGC Explorer up to 3.48.21. The impacted element is an unknown function of the component Password Transmission Handler. Performing a manipulation results in client-side enforcement of server-side security. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitability is regarded as difficult. Upgrading to version 3.48.22 is sufficient to resolve this issue. Upgrading the affected component is recommended. The action taken by the vendor is: "Strengthening of security validation performed on the server side, together with improvements to administrative and authentication controls." The vulnerabilities are limited to NGC Explorer and do not affect other Dígitro products, including UNA and Guardião.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

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

It affects 1 product.


Products: Digitro Ngc Explorer.

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

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

## Is CVE-2025-4527 being exploited?

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

## Other vulnerabilities in Dígitro NGC Explorer

- [CVE-2025-4526](https://insights.sbomify.com/CVE-2025-4526/): Dígitro NGC Explorer Configuration missing password field masking (medium 5.3)
- [CVE-2025-4528](https://insights.sbomify.com/CVE-2025-4528/): Dígitro NGC Explorer session expiration (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4527 is a medium-severity vulnerability in Dígitro NGC Explorer, published on 11 May 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-4527 in the wild and no public exploit code.

Affected product: Dígitro NGC Explorer. 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-4527/ (Markdown: https://insights.sbomify.com/CVE-2025-4527/index.md)
```

## Sources

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

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