Is CVE-2026-105621 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105621 being exploited in the wild.

How severe is CVE-2026-105621?

Medium severity, with a CVSS score of 5.4, published 6 October 2026.

How is CVE-2026-105621 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-105621?

Check whether you run Jishenghua jshERP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105621: jishenghua jshERP improper authorization in financial receipt update

CVE-2026-105621 · Severity: medium · CVSS 5.4 · Published 2026-10-06

jshERP is an open-source ERP system for small and medium businesses that manages sales, purchasing, inventory, and financial operations. A flaw in the financial receipt update handler allows authenticated users to modify audited financial receipts and payments without performing a reverse-audit first, bypassing the approval workflow and corrupting debt settlement records. Additionally, users can modify financial documents belonging to other users in the same tenant.

Technologies: Jishenghua jshERP. Vendors: Jishenghua.

Quick answers

Is CVE-2026-105621 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105621 being exploited in the wild.
How severe is CVE-2026-105621?: Medium severity, with a CVSS score of 5.4, published 6 October 2026.
Which products and versions are affected?: Jishenghua jshERP up to 3.5.
Is there a fix for CVE-2026-105621?: No fixed version is recorded yet. Load and validate the persisted audit status (status='0' for unaudited) in the update handler before allowing modifications, rejecting updates to audited documents. Require an explicit reverse-audit operation before any changes to audited financial documents, and enforce caller ownership and financial-edit permissions on the endpoint.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-105621 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-105621?: Check whether you run Jishenghua jshERP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Load and validate the persisted audit status (status='0' for unaudited) in the update handler before allowing modifications, rejecting updates to audited documents. Require an explicit reverse-audit operation before any changes to audited financial documents, and enforce caller ownership and financial-edit permissions on the endpoint.</anigation> </invoke>

Technical details

The updateAccountHeadAndDetail function in AccountHeadService fails to validate the persisted audit status before updating financial document headers, instead trusting the caller-supplied status value. The update path performs only bill-number uniqueness checks and recalculates settlement details, while the deletion path correctly enforces audit-status validation. An authenticated attacker can modify document amounts and settlement allocations while they remain marked as audited, and the endpoint lacks ownership or data-scope restrictions allowing cross-user modifications within the same tenant.

Affected products

jishenghua jshERP up to 3.5

Timeline

2026-09-17: disclosed: Issue reported on GitHub
2026-10-06: advisory: CVE-2026-105621 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.