CVE-2026-93430

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

GHSA-2fcm-3887-5h6p ↗EUVD-2026-91922 ↗

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.
gdragon GD Rating System <= 3.7.1
ETK-2026-451, permanent identifier
18d 06h 42msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+6h44m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

GD Rating System for WordPress through version 3.7.1 improperly handles certain AJAX render arguments, allowing stored script content to be placed into affected pages. An unauthenticated attacker can abuse the issue when rating items are publicly rendered, because the required per-item nonce is exposed to page visitors.

mitigation

Disable the plugin or restrict public access to pages that render rating items until you can install a vendor release confirmed to address this issue. Treat exposed per-item nonces as public values rather than access control.

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.
0.27%18th percentile
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-03 05:29Z
Δ 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-03 05:29Z
    ghsa: trigger signal, started the run
  2. 2026-10-03 05:29Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-451",
  "cve_id": "CVE-2026-93430",
  "display_id": "CVE-2026-93430",
  "ghsa_id": "GHSA-2fcm-3887-5h6p",
  "euvd_id": "EUVD-2026-91922",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in GD Rating System",
  "summary": "GD Rating System for WordPress through version 3.7.1 improperly handles certain AJAX render arguments, allowing stored script content to be placed into affected pages. An unauthenticated attacker can abuse the issue when rating items are publicly rendered, because the required per-item nonce is exposed to page visitors.",
  "mitigation": "Disable the plugin or restrict public access to pages that render rating items until you can install a vendor release confirmed to address this issue. Treat exposed per-item nonces as public values rather than access control.",
  "vendor": "gdragon",
  "product": "GD Rating System",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.7.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "GD Rating System",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
  "epss_score": 0.0027,
  "epss_percentile": 0.1836,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.708254183333334,
  "t0_at": "2026-10-03T05:29:14.760000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-03T05:29:14.760000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T05:29:14.760000+00:00",
      "url": "https://github.com/advisories/GHSA-2fcm-3887-5h6p"
    }
  }
}

published 2026-10-03 11:47Z
last change 2026-10-21 17:13Z

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.