CVE-2025-13165
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEasyFlow GP developed by Digiwin has a Denial of service vulnerability, allowing unauthenticated remote attackers to send specific requests that result in denial of web service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceEasyFlow GP by Digiwin contains an unauthenticated remote Denial of Service vulnerability. Attackers can send specific requests to the web service that cause it to become unavailable, likely through resource exhaustion or service crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm EasyFlow GP installationCheck system for Digiwin EasyFlow GP software installation. Look for installation directories, services, or running processes related to EasyFlow GP or Digiwin.Affected if EasyFlow GP by Digiwin is installed and running as a web service
-
Identify EasyFlow GP versionCheck the installed version through the software's built-in about page, installation directory files (version.txt, readme, or installer logs), or by querying the web service API if available. Compare against any vendor-released version information.Affected if Version cannot be determined or is any version of EasyFlow GP web service
-
Verify web service accessibilityConfirm the EasyFlow GP web interface is reachable by accessing the application's URL (typically ports 80/443 or custom ports). Test multiple endpoints to confirm basic HTTP response.Affected if The web service is exposed and responds to HTTP requests
-
Check for service availability issuesMonitor the EasyFlow GP service status. Attempt multiple HTTP requests to the web service endpoints and observe response times, error rates, or connection failures.Affected if Service shows intermittent failures, slow responses, or becomes completely unavailable under normal load
-
Review web server access logsExamine EasyFlow GP web server logs (IIS, Apache, or built-in logs) for unusual request patterns, high request volumes from single sources, or anomalous endpoint access that may indicate exploitation attempts.Affected if Logs show patterns consistent with DoS attempts or service degradation
A system is affected if EasyFlow GP by Digiwin is running as a web service and becomes unavailable or unresponsive due to crafted requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement rate limiting and request throttling at the network edge or application level to mitigate mass requests. Apply vendor patches when available and consider deploying a WAF to filter malicious request patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13165 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data