Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13209: XML External Entity Reference in bestfeng oa_git_free

0
Medium
VulnerabilityCVE-2025-13209cvecve-2025-13209
Published: Sat Nov 15 2025 (11/15/2025, 18:32:06 UTC)
Source: CVE Database V5
Vendor/Project: bestfeng
Product: oa_git_free

Description

A weakness has been identified in bestfeng oa_git_free up to 9.5. This affects the function updateWriteBack of the file yimioa-oa9.5\server\c-flow\src\main\java\com\cloudweb\oa\controller\WorkflowPredefineController.java. This manipulation of the argument writeProp causes xml external entity reference. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited.

AI-Powered Analysis

AILast updated: 11/15/2025, 19:31:48 UTC

Technical Analysis

CVE-2025-13209 is an XML External Entity (XXE) vulnerability identified in the bestfeng oa_git_free product, specifically affecting versions 9.0 through 9.5. The vulnerability resides in the updateWriteBack function within the WorkflowPredefineController.java source file. The issue arises from improper handling of the writeProp argument, which is used in XML processing without adequate validation or sanitization, allowing an attacker to inject malicious XML entities. This leads to the XML parser resolving external entities, which can result in disclosure of internal files, server-side request forgery (SSRF), or denial of service (DoS) conditions. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its attack surface. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and low impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although no active exploitation in the wild is reported, a public exploit exists, making it easier for attackers to leverage this flaw. The lack of available patches at the time of reporting necessitates immediate mitigation efforts. The vulnerability affects a critical component of the workflow management system, potentially impacting business processes and sensitive data handled by the application.

Potential Impact

For European organizations, exploitation of this XXE vulnerability could lead to unauthorized disclosure of sensitive internal files or data, potentially exposing confidential business information or personal data protected under GDPR. The partial integrity impact means attackers might manipulate XML data or workflow definitions, disrupting business operations or causing incorrect processing. Availability impacts could result in denial of service, affecting continuity of critical services relying on the oa_git_free platform. Organizations in sectors such as government, finance, healthcare, and manufacturing that use bestfeng oa_git_free for workflow automation are particularly at risk. The remote and unauthenticated nature of the exploit increases the likelihood of attacks, especially if the application is exposed to the internet or accessible from less secure network segments. The presence of a public exploit further elevates the threat, potentially leading to targeted attacks or opportunistic scanning by automated tools. Failure to address this vulnerability could result in regulatory penalties, reputational damage, and operational disruptions.

Mitigation Recommendations

1. Immediately review and apply any available patches or updates from bestfeng once released. 2. If patches are not yet available, disable XML external entity processing in the XML parser configuration used by oa_git_free to prevent resolution of external entities. 3. Implement strict input validation and sanitization on the writeProp argument and any XML inputs to block malicious payloads. 4. Employ network segmentation and firewall rules to restrict outbound HTTP/HTTPS and file system access from the application server to limit the impact of SSRF or file disclosure attempts. 5. Monitor application logs and network traffic for unusual XML payloads or access patterns indicative of exploitation attempts. 6. Conduct a security review of all XML processing components in the environment to identify and remediate similar XXE risks. 7. Educate developers and administrators about secure XML handling practices and the risks of XXE vulnerabilities. 8. Consider deploying web application firewalls (WAFs) with rules to detect and block XXE attack patterns targeting the affected endpoints.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-11-14T19:00:50.250Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6918d42bcdb3e870ee534ce6

Added to database: 11/15/2025, 7:27:39 PM

Last enriched: 11/15/2025, 7:31:48 PM

Last updated: 11/16/2025, 2:49:52 AM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats