CVE-2025-13209VulnerabilityPublished 15 Nov 2025Updated 17 Nov 2025

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

Affects bestfeng oa_git_freeSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavencom.cloudweb/oa_git_free`pkg:maven/com.cloudweb/oa_git_free`Other threats	Affected =9.0 =9.1 =9.2 =9.3 =9.4 =9.5	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately audit their deployments of bestfeng oa_git_free to identify affected versions (9.0 to 9.5). Until official patches are released, administrators should implement the following mitigations: 1) Disable XML external entity processing in the Java XML parsers used by the application, typically by setting features such as 'http://apache.org/xml/features/disallow-doctype-decl' to true and disabling external entity resolution. 2) Employ Web Application Firewalls (WAFs) with rules to detect and block XXE attack patterns targeting the updateWriteBack endpoint. 3) Restrict network access to the application to trusted IPs and internal networks to reduce exposure. 4) Monitor logs for suspicious XML payloads or anomalies in workflow update requests. 5) Conduct code reviews and static analysis to identify and remediate unsafe XML parsing practices in custom integrations. 6) Prepare for patch deployment by tracking vendor advisories and testing updates in isolated environments. 7) Educate developers and security teams on secure XML handling best practices to prevent recurrence.

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.

Impact

For European organizations, exploitation of CVE-2025-13209 could result in unauthorized disclosure of sensitive internal files, potentially exposing confidential business data or credentials. Integrity could be compromised if attackers manipulate XML data to alter workflow definitions or configurations, leading to unauthorized process changes. Availability impacts may arise from DoS attacks triggered by malicious XML payloads causing resource exhaustion. Organizations relying on bestfeng oa_git_free for workflow automation or document management could face operational disruptions. Given the remote exploitability without user interaction, attackers could automate attacks at scale, increasing risk to critical infrastructure and enterprises. Data privacy regulations such as GDPR heighten the consequences of data leaks resulting from this vulnerability. The medium severity score suggests moderate but non-trivial risk, warranting prompt mitigation especially in sectors handling sensitive or regulated data.

Summary

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. This function improperly processes the writeProp argument, allowing an attacker to inject malicious XML entities. When the application parses this crafted XML input, it can be tricked into resolving external entities, which may lead to disclosure of internal files, server-side request forgery (SSRF), or denial of service (DoS) conditions. The vulnerability is remotely exploitable without user interaction and requires only low-level privileges, increasing its risk profile. The CVSS 4.0 base score is 5.3, reflecting medium severity due to limited scope and partial impact on confidentiality, integrity, and availability. Although no official patches or mitigations have been published yet, the public availability of exploit code increases the urgency for defensive measures. The vulnerability does not require authentication, making exposed instances particularly vulnerable to automated scanning and exploitation attempts. The lack of scope change indicates the vulnerability affects only the vulnerable component without impacting other system components. This flaw highlights the importance of secure XML parsing practices, such as disabling external entity resolution and validating input data.

References

Community reviews

Loading reviews…