dbcve.org
XML External Entity (XXE)Weakness · CWE-611

CVE-2023-7307

HIGH · 8.7 CVSS v4.0 Published 2025-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
Sangfor Behavior Management System (also referred to as DC Management System in Chinese-language documentation) contains an XML external entity (XXE) injection vulnerability in the /src/sangforindex endpoint. A remote unauthenticated attacker can submit crafted XML data containing external entity definitions, leading to potential disclosure of internal files, server-side request forgery (SSRF), or other impacts depending on parser behavior. The vulnerability is due to improper configuration of the XML parser, which allows resolution of external entities without restriction. This product is now integrated into their IAM (Internet Access Management) platform and an affected version range is undefined. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-09-06 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 · moderate confidence

Sangfor Behavior Management System contains an XXE injection vulnerability in the /src/sangforindex endpoint. A remote unauthenticated attacker can submit crafted XML containing external entity definitions, allowing disclosure of internal files, SSRF, or other impacts due to the XML parser being configured to allow resolution of external entities without restriction.

MitigationDisable external entity resolution in the XML parser used by the /src/sangforindex endpoint, or restrict network access to the endpoint if patching is not feasible. Consider Web Application Firewall rules to detect and block XXE payloads.

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:N/VA:N/SC:N/SI:N/SA:N/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 Sangfor Behavior Management System installation
    Locate the installation directory and find version information files, typically in the product's main directory or configuration folder. Check for files like version.conf, about.ini, or consult the product's web interface admin panel for the version details.
    Affected if The product is installed and the version cannot be confirmed as patched or is within an unknown affected range.
  2. Verify /src/sangforindex endpoint is accessible
    Attempt to access the endpoint via HTTP/HTTPS request (e.g., GET or POST to https://yourhost/src/sangforindex). Check if the endpoint responds and accepts XML input.
    Affected if The endpoint is exposed and accepts XML requests without proper validation.
  3. Review XML parser configuration
    Examine the application's XML parser configuration files or source code that handles the /src/sangforindex endpoint. Look for parser settings related to external entity resolution, DTD processing, and entity expansion.
    Affected if The XML parser is configured with external entity resolution enabled or DTD processing allowed.
  4. Test for XXE vulnerability safely
    Submit a benign XXE test payload to the /src/sangforindex endpoint using a POST request with Content-Type: application/xml. Use a limited external entity reference that triggers an out-of-band callback to a controlled test endpoint. Monitor for callback requests.
    Affected if The application processes external entities and makes outbound network requests to the test endpoint, confirming XXE is exploitable.

The environment is affected if Sangfor Behavior Management System is running with an unpatched version and the /src/sangforindex endpoint processes XML without disabling external entity resolution.

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

Disable external entity resolution in the XML parser used by the /src/sangforindex endpoint, or restrict network access to the endpoint if patching is not feasible. Consider Web Application Firewall rules to detect and block XXE payloads.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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