LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25082: zwczou WeChat SDK Python to_xml xml external entity reference

A vulnerability was found in zwczou WeChat SDK Python 0.3.0 and classified as critical. This issue affects the function validate/to_xml. The manipulation leads to xml external entity reference. The attack may be initiated remotely. Upgrading to version 0.5.5 is able to address this issue. The patch is named e54abadc777715b6dcb545c13214d1dea63df6c9. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-223403.

MediumCVSS 6.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-25082 is an XML external entity issue in zwczou WeChat SDK Python 0.3.0. If an application processes attacker-controlled XML through the affected SDK function, the XML parser may access unintended local or internal resources. The named fix is upgrading to version 0.5.5.

Executive priority

Treat this as a targeted dependency remediation item, not a broad emergency. Upgrade any affected WeChat integration promptly, especially internet-facing services, because XXE can expose sensitive internal data or disrupt service behavior.

Technical view

The sources identify CWE-611 in the validate/to_xml function of zwczou WeChat SDK Python 0.3.0. VulDB rates the issue as remotely initiable with CVSS v2 6.5, requiring authentication and allowing partial confidentiality, integrity, and availability impact. Patch commit e54abadc777715b6dcb545c13214d1dea63df6c9 and release v0.5.5 address it.

Likely exposure

Exposure is likely limited to Python applications using zwczou WeChat SDK Python 0.3.0 and processing XML from remote or semi-trusted users through the affected validate/to_xml path.

Exploitation context

The bundle says the attack may be initiated remotely, but CVSS indicates authentication is required. KEV is false, and the provided sources do not claim active exploitation or public weaponization.

Researcher notes

Evidence is strongest for affected version, vulnerable function, CWE, CVSS, and fixed release. The bundle does not provide exploit details, affected downstream products, or active exploitation evidence. Validate exposure by mapping actual XML inputs into the SDK.

Mitigation direction

  • Upgrade zwczou WeChat SDK Python to version 0.5.5 or later.
  • Confirm the deployed package includes patch commit e54abadc777715b6dcb545c13214d1dea63df6c9.
  • Check vendor guidance before applying alternate mitigations.
  • Prioritize services that parse external XML through this SDK.

Validation and detection

  • Search dependency manifests for zwczou WeChat SDK Python version 0.3.0.
  • Confirm runtime environments load version 0.5.5 or a patched build.
  • Identify code paths invoking validate/to_xml with untrusted XML input.
  • Run regression tests for WeChat XML processing after upgrading.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-611: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-25082 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 2.0MediumAV:N/AC:L/Au:S/C:P/I:P/A:P86.4Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

6.5Medium
CVSS 2.0 vector shape for CVE-2018-25082Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
zwczouWeChat SDK Python0.3.0Listed
Weakness

CWE details

CWE-611

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs