CVE-2026-120347

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

GHSA-rq2r-g99g-gxmf ↗EUVD-2026-115069 ↗

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.
dayrui XunRuiCMS 4.7.0; 4.7.1; 4.7.2; 4.7.3; 4.7.4
ETK-2026-3272Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 32msince last run
1h 58mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h54m
0
+2h
+6h
+8h
+10h
+12h

description

dayrui XunRuiCMS versions through 4.7.4 contain an SQL injection flaw in the Member Module View handler. A remote unauthenticated attacker may execute unintended database queries where the affected request path is exposed.

mitigation

Upgrade XunRuiCMS to a release that includes patch 9b6ea0cf9c6e8cdc9a5260c38b95da5fed4c4231. Until upgraded, restrict public access to the affected Member Module request path.

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
1h 58m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-02 05:30Z
Δ 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-11-02 05:30Z
    ghsa: trigger signal, started the run
  2. 2026-11-02 05:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3272",
  "cve_id": "CVE-2026-120347",
  "display_id": "CVE-2026-120347",
  "ghsa_id": "GHSA-rq2r-g99g-gxmf",
  "euvd_id": "EUVD-2026-115069",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in dayrui XunRuiCMS Member Module",
  "summary": "dayrui XunRuiCMS versions through 4.7.4 contain an SQL injection flaw in the Member Module View handler. A remote unauthenticated attacker may execute unintended database queries where the affected request path is exposed.",
  "mitigation": "Upgrade XunRuiCMS to a release that includes patch 9b6ea0cf9c6e8cdc9a5260c38b95da5fed4c4231. Until upgraded, restrict public access to the affected Member Module request path.",
  "vendor": "dayrui",
  "product": "XunRuiCMS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "4.7.0",
        "4.7.1",
        "4.7.2",
        "4.7.3",
        "4.7.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "XunRuiCMS",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 117.80317275,
  "t0_at": "2026-11-02T05:30:30.380000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T05:30:30.380000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T05:30:30.380000+00:00",
      "url": "https://github.com/advisories/GHSA-rq2r-g99g-gxmf"
    }
  }
}

published 2026-11-02 07:27Z
last change 2026-11-02 12:55Z

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.