dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-66744

HIGH · 7.5 CVSS v3.1 Published 2026-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
In Yonyou YonBIP v3 and before, the LoginWithV8 interface in the series data application service system is vulnerable to path traversal, allowing unauthorized access to sensitive information within the system

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 confidence

Path traversal vulnerability in the LoginWithV8 interface of Yonyou YonBIP v3 allows attackers to use directory traversal sequences (e.g., ../../) to access sensitive files outside the web root, potentially exposing configuration files, credentials, or other confidential system data.

MitigationImplement strict input validation and path canonicalization on the LoginWithV8 interface to normalize and verify all file paths before access; deploy WAF rules to detect and block directory traversal patterns; apply principle of least privilege to restrict filesystem access permissions.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify LoginWithV8 interface is exposed
    Check if the LoginWithV8 endpoint is accessible in your Yonyou YonBIP installation. This is typically found at paths like /uapim/ LoginWithV8 or /service/ LoginWithV8. Use curl or a browser to attempt accessing this endpoint.
    Affected if The LoginWithV8 interface is publicly or internally accessible without authentication or with low-privilege authentication.
  2. Identify YonBIP version
    Check the installed YonBIP version by inspecting version files in the installation directory, typically in config files like version.properties, about.xml, or the system administration panel.
    Affected if The installed version is YonBIP v3 (any minor version), as the vulnerability specifically affects this version line.
  3. Test for path traversal vulnerability
    Send a request to the LoginWithV8 interface with directory traversal sequences, such as ../../../../etc/passwd or ../../../../windows/win.ini, as a parameter value. Observe if the response returns file contents from outside the web root.
    Affected if The interface returns file contents from paths outside the intended web root directory, indicating the path traversal is successful.
  4. Check for input validation on file paths
    Review the web application firewall (WAF) configuration or input validation settings for the LoginWithV8 interface to determine if directory traversal patterns (../, ..\) are being filtered or blocked.
    Affected if No input validation or path canonicalization is configured for the LoginWithV8 interface, allowing traversal sequences to pass through.
  5. Audit filesystem permissions
    Check the filesystem permissions on sensitive directories (such as configuration, system, and application data folders) to determine if the web application process has unnecessary read access to files outside its intended scope.
    Affected if The web application process has broad read permissions that allow accessing sensitive configuration or system files through the traversal vulnerability.

A user is affected if they run Yonyou YonBIP v3 with the LoginWithV8 interface exposed and without input validation or path canonicalization preventing directory traversal sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and path canonicalization on the LoginWithV8 interface to normalize and verify all file paths before access; deploy WAF rules to detect and block directory traversal patterns; apply principle of least privilege to restrict filesystem access permissions.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66744 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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