dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-34039

CRITICAL · 10.0 CVSS v4.0 Published 2025-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A code injection vulnerability exists in Yonyou UFIDA NC v6.5 and prior due to the exposure of the BeanShell testing servlet (bsh.servlet.BshServlet) without proper access controls. The servlet allows unauthenticated remote attackers to execute arbitrary Java code via the bsh.script parameter. This can be exploited to run system commands and ultimately gain full control over the target server. The issue is rooted in a third-party JAR component bundled with the application, and the servlet is accessible without authentication on vulnerable installations. Exploitation evidence was observed by the Shadowserver Foundation on 2025-02-05 UTC.

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 · high confidence

Yonyou UFIDA NC v6.5 and prior exposes the BeanShell testing servlet (bsh.servlet.BshServlet) from a bundled third-party JAR without any authentication. Unauthenticated remote attackers can inject and execute arbitrary Java code through the bsh.script parameter, enabling full system command execution and complete server compromise.

MitigationImmediately restrict or disable the bsh.servlet.BeshServlet endpoint, remove the vulnerable BeanShell JAR from the application, or deploy authentication controls on the servlet. Network segmentation can limit exposure until proper remediation is applied.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify Yonyou UFIDA NC installation
    Locate the UFIDA NC installation directory - commonly found under /nc, /ufida/nc, or C:/ufida/nc in the application server's webapp folder. Check for the presence of nc.jar or UFTaskHandler.class files.
    Affected if The product is installed on the system.
  2. Determine installed UFIDA NC version
    Check the version by inspecting the NC's version file (often named version.properties, version.ini, or in the about page of the web interface), or by querying the NC's built-in version endpoint if available. Compare against v6.5 and prior.
    Affected if The installed version is Yonyou UFIDA NC v6.5 or any prior version.
  3. Verify BeanShell servlet is exposed
    Attempt to access the BeanShell testing servlet endpoint - typically at paths like /servlet/bsh.servlet.BshServlet, /bsh, /beanShell, or /bsh.servlet.BshServlet under the NC context. Send an HTTP GET request without authentication credentials.
    Affected if The servlet responds with a BeanShell interpreter page or accepts bsh.script parameters without requiring authentication.
  4. Check for vulnerable BeanShell JAR
    Search for the bsh.jar file in the application lib directories - commonly in WEB-INF/lib or nc_home/lib folders. Typical filenames include bsh-2.0.jar, bsh-1.3.0.jar, or beanshell-2.x.jar.
    Affected if The BeanShell JAR file exists in the application deployment.
  5. Test for remote code execution
    Send a benign HTTP POST request to the BeanShell servlet endpoint with parameter bsh.script=print(getProperty("java.version")); to verify code execution capability. This should return Java version information if vulnerable.
    Affected if The server executes the BeanShell script and returns the result without authentication.

A user is affected if Yonyou UFIDA NC v6.5 or prior is installed AND the BeanShell servlet (bsh.servlet.BshServlet) is accessible without authentication, allowing arbitrary code execution via the bsh.script parameter.

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

Immediately restrict or disable the bsh.servlet.BeshServlet endpoint, remove the vulnerable BeanShell JAR from the application, or deploy authentication controls on the servlet. Network segmentation can limit exposure until proper remediation is applied.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34039 — 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-34039 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