CVE-2022-51022

waiting for further signalsZero needs more public information before it can validate it.

GHSA-g786-pwww-f3jp ↗EUVD-2022-56066 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
liukuo362573 YiShaAdmin >= 2.2, <= 3.1
ETK-2026-2438Zero's internal tracking ID, independent of the CVE number., permanent identifier
14msince last run
38mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h35m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

YiShaAdmin versions 2.2 through 3.1 are affected by a path traversal flaw in the file-download functionality. An unauthenticated remote attacker may access or delete files outside the intended directory when the affected endpoint is reachable.

mitigation

Apply commit 025b062, or upgrade to a release confirmed to contain it. Until patched, restrict access to the affected administrative endpoint to trusted networks and authenticated reverse-proxy controls.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
38m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 10:57Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-22 10:57Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 10:57Z

this entry in the feed

GET /api/v1/feed/CVE-2022-51022

{
  "etk_id": "ETK-2026-2438",
  "cve_id": "CVE-2022-51022",
  "display_id": "CVE-2022-51022",
  "ghsa_id": "GHSA-g786-pwww-f3jp",
  "euvd_id": "EUVD-2022-56066",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated path traversal in YiShaAdmin",
  "summary": "YiShaAdmin versions 2.2 through 3.1 are affected by a path traversal flaw in the file-download functionality. An unauthenticated remote attacker may access or delete files outside the intended directory when the affected endpoint is reachable.",
  "mitigation": "Apply commit 025b062, or upgrade to a release confirmed to contain it. Until patched, restrict access to the affected administrative endpoint to trusted networks and authenticated reverse-proxy controls.",
  "vendor": "liukuo362573",
  "product": "YiShaAdmin",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.2, <= 3.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "YiShaAdmin",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.28810685,
  "t0_at": "2026-10-22T10:57:33.205000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T10:57:33.205000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T10:57:33.205000+00:00",
      "url": "https://github.com/advisories/GHSA-g786-pwww-f3jp"
    }
  }
}

published 2026-10-22 12:54Z
last change 2026-10-22 13:39Z

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.