CVE-2025-13209
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 · uneditedA 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.
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 confidenceThis is an XML External Entity (XXE) injection vulnerability in bestfeng oa_git_free up to version 9.5. The updateWriteBack function in WorkflowPrehandleController.java processes user-controlled input (writeProp) without proper sanitization, allowing attackers to inject malicious XML with external entity references. This can lead to disclosure of local files, denial of service, or server-side request forgery.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if bestfeng oa_git_free is installedLocate the application deployment directory and identify the installed version by checking version files, build artifacts, or the application banner. Compare the version number to 9.5 (inclusive).Affected if The application is bestfeng oa_git_free version 9.5 or lower
-
Locate the affected Java source fileSearch for the file WorkflowPrehandleController.java within the application source code or decompiled bytecode. This file contains the vulnerable updateWriteBack function.Affected if The file exists and contains the updateWriteBack function handling the writeProp parameter
-
Verify XML parsing without entity protectionExamine the updateWriteBack function code to confirm it parses the writeProp parameter as XML. Check if the XML parser is configured with disallow-doctype-decl=true, external-general-entities=false, or external-parameter-entities=false.Affected if The code parses writeProp as XML without disabling external entities and DTD processing
-
Confirm writeProp parameter is user-controllableTrace how the writeProp parameter enters the updateWriteBack function - verify it comes directly from an HTTP request parameter without input validation or sanitization before XML parsing.Affected if The writeProp parameter flows from user input directly to the XML parser without validation
A user is affected if bestfeng oa_git_free version 9.5 or lower is running and the WorkflowPrehandleController.java updateWriteBack function parses the writeProp parameter as XML without disabling external entity processing.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable external entity processing and DTD parsing in the XML parser configuration within the affected function, and implement input validation for the writeProp parameter before XML parsing.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13209 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13209 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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