CVE-2026-1218
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 vulnerability was detected in Bjskzy Zhiyou ERP up to 11.0. Impacted is the function initRCForm of the file RichClientService.class of the component com.artery.richclient.RichClientService. Performing a manipulation results in xml external entity reference. The attack is possible to be carried out remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceXML External Entity (XXE) injection vulnerability in the initRCForm function of RichClientService.class in Bjskzy Zhiyou ERP up to v11.0 allows remote attackers to reference external XML entities by crafting malicious XML input, potentially leading to disclosure of internal 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 Bjskzy Zhiyou ERP is installedLocate the ERP installation directory and check for version information in the application metadata, configuration files, or about/version pageAffected if The installed version is Bjskzy Zhiyou ERP and the version is v11.0 or earlier
-
Confirm the RichClientService component existsLocate RichClientService.class within the application deployment (typically in WEB-INF/lib or the compiled classes directory)Affected if The RichClientService.class file exists in the application and is loaded at runtime
-
Verify if the initRCForm function is exposedReview application routing or web service endpoints to determine if initRCForm can receive HTTP requests (typically via SOAP or REST interface on the service endpoint)Affected if The initRCForm function is accessible via a network-exposed endpoint and accepts XML input
-
Check XML parser configuration for the serviceExamine the XML parser initialization code or configuration for RichClientService to determine whether external entity processing and DTD processing are enabledAffected if The XML parser is configured to allow external entity processing or DTD parsing without restrictions
-
Test for XXE vulnerability (if authorized)Send a crafted XML payload with an external entity reference to the initRCForm endpoint and observe if the parser resolves the external entityAffected if The XML parser processes external entity references and returns resolved content or makes outbound requests to attacker-controlled servers
A user is affected if Bjskzy Zhiyou ERP version 11.0 or earlier is installed, the RichClientService with initRCForm is network-accessible, and the XML parser allows 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 processing in the XML parser configuration used by the RichClientService, implement input validation for XML payloads, and consider upgrading to a patched version if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1218 — 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-2026-1218 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