Quick answers
- Is CVE-2026-11469 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11469 being exploited in the wild.
- How severe is CVE-2026-11469?
- Medium severity, with a CVSS score of 4.7, published 8 June 2026.
- Which products and versions are affected?
- Jishenghua jshERP up to 3.6.
- Is there a fix for CVE-2026-11469?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. 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-11469 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-11469?
- 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.
Technical details
A stored Server-Side Request Forgery (SSRF) vulnerability exists in jshERP-boot up to version 3.6. The flaw is located in the `insertPlatformConfig` function within `PlatformConfigService.java`. An attacker with administrative privileges can submit a malicious URL via the `platformValue` parameter at the `/platformConfig/add` endpoint (specifically when `platformKey` is set to `weixinUrl`). This value is persisted in the database without validation. When the system later invokes WeChat-related functions like `getAccessToken`, it retrieves the stored URL and passes it to `HttpClient.httpGet()`. This allows an attacker to trigger arbitrary outbound GET requests to internal services or cloud metadata endpoints. As of the advisory date, no official patch has been released.
Affected products
- jishenghua jshERP up to 3.6
Timeline
- 2026-05-19: disclosed: Issue reported on GitHub repository
- 2026-06-08: advisory: VulDB and NVD publication