Security readout for executives and security teams
Plain-English summary
CVE-2026-1218 affects Bjskzy Zhiyou ERP 11.0. A remote, authenticated attacker may be able to abuse XML processing in the RichClientService initRCForm function. The reported impact includes confidentiality, integrity, and availability effects. Public exploit information is reported, but CISA KEV does not list active exploitation.
Executive priority
Treat as a near-term ERP security review item, not an emergency absent active exploitation evidence. Prioritize if Zhiyou ERP 11.0 is externally reachable, widely used by partners, or contains sensitive business data.
Technical view
The issue is an XML External Entity-related flaw mapped to CWE-610 and CWE-611 in com.artery.richclient.RichClientService, RichClientService.class, initRCForm. VulDB rates it CVSS 2.0 6.5 with AV:N/AC:L/Au:S/C:P/I:P/A:P. The vendor reportedly did not respond, and no vendor fix is named in the provided sources.
Likely exposure
Organizations running Bjskzy Zhiyou ERP version 11.0 are the stated affected population. Exposure is higher if RichClientService is reachable by authenticated users over a network. The sources do not identify other affected versions, deployment patterns, or internet-exposure prevalence.
Exploitation context
The source bundle says an exploit is public and may be used. It also indicates authentication is required. There is no cited evidence of active exploitation, and the CVE is not marked as CISA KEV in the provided data.
Researcher notes
Evidence is limited to CVE/VulDB-style reporting and a referenced public write-up. The GitHub reference is tagged as exploit and broken-link in the bundle, so avoid assuming availability beyond the bundle’s statement. No patch, workaround, or vendor advisory is included.
Mitigation direction
- Identify whether Bjskzy Zhiyou ERP 11.0 is deployed.
- Restrict network access to ERP rich client services to trusted users and networks.
- Review vendor or integrator guidance for updates or supported mitigations.
- Monitor ERP logs for unusual authenticated RichClientService activity.
- Apply compensating controls until vendor remediation is confirmed.
Validation and detection
- Confirm product name and version from asset inventory or application administration.
- Determine whether RichClientService is enabled and network reachable.
- Check whether access requires authentication in your deployment.
- Review logs for anomalous requests involving initRCForm or XML processing.
- Track VulDB, CVE, and vendor channels for remediation updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-610: 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 lookupCWE-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 lookupCVE-2026-1218 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
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.
CVSS vector scores
1 official scoreWe 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.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341908 | Bjskzy Zhiyou ERP com.artery.richclient.RichClientService RichClientService.class initRCForm xml external entity referenceCVE reference · vdb-entry, technical-description
- VDB-341908 | CTI Indicators (IOB, IOC, IOA)CVE reference · signature, permissions-required
- Submit #735201 | Bjskzy Enterprise Resource Planning Software 11.0 XML External Entity ReferenceCVE reference · third-party-advisory
- https://github.com/dingpotian/cve-vul/blob/main/Shikong-Zhiyou-ERP/Shikong-Zhiyou-ERP-XXE-RichClientService-initRCForm.mdCVE reference · broken-link, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Externally Controlled Reference to a Resource in Another Sphere
Externally Controlled Reference to a Resource in Another Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.