{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109187 exists.","fix":"No fix has been published for CVE-2026-109187 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-109187 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109187 exists.\n\nAffected product: jishenghua jshERP. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-109187/ (Markdown: https://insights.sbomify.com/CVE-2026-109187/index.md)","id":"CVE-2026-109187","markdown":"https://insights.sbomify.com/CVE-2026-109187/index.md","name":"CVE-2026-109187","record":{"aliases":["GHSA-47x2-rrvv-xffp"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ERP system","requires_auth":"low_privilege","summary":"Authenticated users can read sensitive platform configuration secrets like SMTP codes via an insecure API endpoint in jshERP.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"jshERP through 3.6 Information Disclosure via /platformConfig/getInfoByKey","id":"CVE-2026-109187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"jshERP through 3.6 Missing Authorization in Master Data Add and Import Endpoints","id":"CVE-2026-109188"},"packages":[],"prev":{"headline":"jshERP through 3.6 Mass Assignment via PUT /user/update","id":"CVE-2026-109186"},"products":["jshERP"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["jishenghua"]},"summary":"Authenticated users can read sensitive platform configuration secrets like SMTP codes via an insecure API endpoint in jshERP.","url":"https://insights.sbomify.com/CVE-2026-109187/"}