# CVE-2026-109187: jshERP through 3.6 Information Disclosure via /platformConfig/getInfoByKey

> Authenticated users can read sensitive platform configuration secrets like SMTP codes via an insecure API endpoint in jshERP.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 12 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-47x2-rrvv-xffp

## What is CVE-2026-109187?

CVE-2026-109187 is a high-severity vulnerability in jishenghua jshERP, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

jshERP through 3.6 contains an information disclosure vulnerability that allows any authenticated user to read platform-wide configuration secrets via the getInfoByKey handler of PlatformConfigController. Low-privilege users of any tenant can request arbitrary platformKey values such as email_auth_code or activation_code to obtain SMTP authorization codes and activation secrets, because only aliOss and weixin keys are blocked.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109187 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109187 is a high-severity vulnerability in jishenghua jshERP, published on 12 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-109187 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-109187/ (Markdown: https://insights.sbomify.com/CVE-2026-109187/index.md)
```

## Sources

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

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