# CVE-2026-1218: XML external entity in Zhiyou ERP

> Remote attackers can exploit an XML External Entity vulnerability in Zhiyou ERP to read sensitive data or cause denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-2gpj-j2rf-2376

## What is CVE-2026-1218?

CVE-2026-1218 is a medium-severity vulnerability in Bjskzy Zhiyou ERP, published on 20 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A 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.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference), CWE-610 (Externally Controlled Reference to a Resource in Another Sphere)

## Which versions are affected by CVE-2026-1218?


## How do I fix CVE-2026-1218?

No fix has been published for CVE-2026-1218 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1218 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1218 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1218 and fix it if it is affected.

What it is: CVE-2026-1218 is a medium-severity vulnerability in Bjskzy Zhiyou ERP, published on 20 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1218 exists.

Affected product: Bjskzy Zhiyou ERP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1218/ (Markdown: https://insights.sbomify.com/CVE-2026-1218/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1218
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1218
- OSV: https://osv.dev/vulnerability/CVE-2026-1218

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1218/
Summaries are generated and may contain mistakes; the official description above is the record.