# CVE-2025-13163: Digiwin｜EasyFlow GP - Insufficiently Protected Credentials

> Privileged remote attackers can obtain plaintext database credentials from the frontend of Digiwin EasyFlow GP.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-637m-5wp2-vxwg

## What is CVE-2025-13163?

CVE-2025-13163 is a medium-severity vulnerability in Digiwin EasyFlow GP, published on 17 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

EasyFlow GP developed by Digiwin has an Insufficiently Protected Credentials vulnerability, allowing privileged remote attackers to obtain plaintext database account credentials from the system frontend.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2025-13163 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13163 is a medium-severity vulnerability in Digiwin EasyFlow GP, published on 17 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13163 in the wild and no public exploit code.

Affected product: Digiwin EasyFlow GP. 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-13163/ (Markdown: https://insights.sbomify.com/CVE-2025-13163/index.md)
```

## Sources

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

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