# CVE-2026-105621: jishenghua jshERP Financial Receipt Update AccountHeadService.java updateAccountHeadAndDetail improper authorization

> Attackers can remotely modify financial receipt data in jshERP due to missing authorization checks in the update function.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-57gg-hg4f-x2j5

## What is CVE-2026-105621?

CVE-2026-105621 is a medium-severity missing authorization vulnerability in jishenghua jshERP, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in jishenghua jshERP up to 3.5. Affected is the function updateAccountHeadAndDetail of the file jshERP-boot/src/main/java/com/jsh/erp/service/AccountHeadService.java of the component Financial Receipt Update Handler. Performing a manipulation results in improper authorization. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-105621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105621 is a medium-severity missing authorization vulnerability in jishenghua jshERP, published on 6 Oct 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-105621 exists.

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

## Sources

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

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