CVE-2026-109187

waiting for further signals

EUVD-2026-97391 ↗

no check availablenot proven exploitable

cve.orgpublic poc+0mkev

jishenghua jshERP <= 3.6

CWE-862 Missing Authorization

ETK-2026-1385, permanent identifier

cvss7.1cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

8d 11h 20msince last run

32mAI analysis

timeline

0 = trigger signal

trigger signal (cve.org) +0hpublic poc+0hwaiting for further signals+4h18m

+2h

+6h

+8h

+10h

+12h

description

jshERP versions through 3.6 may allow authenticated users with low tenant privileges to retrieve sensitive system-wide configuration values. An attacker needs a valid account and access to the configuration lookup capability.

mitigation

Restrict access to the affected configuration lookup capability to trusted administrators and rotate any potentially exposed SMTP and activation credentials. Upgrade to a vendor-fixed release when one is published; no fixed version is recorded in the advisory evidence.

check

exploit

automation

contextual

auth required

yes, low privileges

EPSS

0.25%15th percentile

agent run time

32m

cve.org record, t = 0

2026-10-12 13:10Z

Δ to public poc

+0m

Δ to kev

–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

2026-10-12 13:10Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-109187
2026-10-12 17:01Z
exploit reference (github.com)
github · https://github.com/AnkesKasty/cve-request-poc/blob/a7b6d1423555812d8efa26c91c5d0683164b31e5/jshERP/poc_global_config_and_enumeration.py

this entry in the feed

GET /api/v1/feed/CVE-2026-109187

{
  "etk_id": "ETK-2026-1385",
  "cve_id": "CVE-2026-109187",
  "display_id": "CVE-2026-109187",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-97391",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated configuration secret disclosure in jshERP",
  "summary": "jshERP versions through 3.6 may allow authenticated users with low tenant privileges to retrieve sensitive system-wide configuration values. An attacker needs a valid account and access to the configuration lookup capability.",
  "mitigation": "Restrict access to the affected configuration lookup capability to trusted administrators and rotate any potentially exposed SMTP and activation credentials. Upgrade to a vendor-fixed release when one is published; no fixed version is recorded in the advisory evidence.",
  "vendor": "jishenghua",
  "product": "jshERP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "jshERP",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_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",
  "epss_score": 0.0025,
  "epss_percentile": 0.1506,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.6534963,
  "t0_at": "2026-10-12T13:10:46.387000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-12T13:10:46.387000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T13:10:46.387000+00:00",
      "url": "https://github.com/AnkesKasty/cve-request-poc/blob/a7b6d1423555812d8efa26c91c5d0683164b31e5/jshERP/poc_global_config_and_enumeration.py"
    },
    "trigger_signal": {
      "at": "2026-10-12T13:10:46.387000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T13:10:46.387000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-109187"
    }
  }
}

published 2026-10-12 16:57Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.