Loading vulnerability…
CVE-2025-34039 is a code injection vulnerability affecting Yonyou UFIDA NC version 6.5 and earlier. The issue arises because the BeanShell testing servlet, bsh.servlet.BshServlet, is exposed in deployed installations without proper access controls. This servlet accepts attacker-supplied code through the bsh.script parameter and evaluates it as Java/BeanShell code. Because the endpoint is accessible without authentication, a remote attacker can submit arbitrary code for execution in the context of the application server. The vulnerable component appears to originate from a bundled third-party JAR included with the product. Successful exploitation enables execution of system commands and can lead to full compromise of the underlying server. Exploitation in the wild was observed by the Shadowserver Foundation on 2025-02-05 UTC.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.