# CVE-2026-85040: ZhongBangKeJi CRMEB Custom Scheduled Task Feature save eval os command injection

> Remote attackers with admin privileges can execute arbitrary OS commands via the custom scheduled task feature due to unsafe code evaluation.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-q67v-wjjm-5rv3

## What is CVE-2026-85040?

CVE-2026-85040 is a medium-severity command injection vulnerability in ZhongBangKeJi CRMEB, published on 3 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A weakness has been identified in ZhongBangKeJi CRMEB up to 6.0.0. Affected by this vulnerability is the function eval of the file /adminapi/system/crontab/save of the component Custom Scheduled Task Feature. This manipulation of the argument customCode causes os command injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. Vendor documents this as deliberate debug-only behavior. But isSafePhpCode blacklist offers no real RCE containment.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-85040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85040 is a medium-severity command injection vulnerability in ZhongBangKeJi CRMEB, published on 3 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85040 exists.

Affected product: ZhongBangKeJi CRMEB. 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-85040/ (Markdown: https://insights.sbomify.com/CVE-2026-85040/index.md)
```

## Sources

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

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