Quick answers
- Is CVE-2026-105325 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105325 being exploited in the wild.
- How severe is CVE-2026-105325?
- Informational severity, published 5 November 2026.
- Which products and versions are affected?
- <UNKNOWN> before 24.09.08.
- Is there a fix for CVE-2026-105325?
- Yes: fixed in 24.09.08. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105325 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-105325?
- Check whether you run <UNKNOWN> 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
- Fixed in: 24.09.08
Technical details
A missing authorization check in the accounting module fails to enforce ACCOUNTING_UPDATE and ACCOUNTING_CREATE permissions before allowing operations on PaymentApplication records. An attacker with only ACCOUNTING_VIEW permission can exploit this to bypass intended access controls and perform unauthorized create and update operations on accounting data.
Affected products
- <UNKNOWN> before 24.09.08
Timeline
- 2026-11-05: disclosed