CVE-2026-129151

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

GHSA-qhjv-j3c3-593v ↗EUVD-2026-125615 ↗

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.
javahuang SurveyKing 1.13.2
CWE-862 Missing Authorization
ETK-2026-4413Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 41msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h39m
0
+4h
+6h
+8h
+10h
+12h

description

SurveyKing 1.13.2 has an authorization flaw affecting survey result lookup. An unauthenticated attacker with a public survey link may bypass lookup protections and access response data, including hidden fields.

mitigation

Restrict or remove public survey links and block unauthenticated access to result-lookup functionality where possible. Require authorization before exposing lookup configuration or response data, and monitor for a vendor update.

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.
contextual
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
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 17:22Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-13 17:22Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4413",
  "cve_id": "CVE-2026-129151",
  "display_id": "CVE-2026-129151",
  "ghsa_id": "GHSA-qhjv-j3c3-593v",
  "euvd_id": "EUVD-2026-125615",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in SurveyKing result lookup",
  "summary": "SurveyKing 1.13.2 has an authorization flaw affecting survey result lookup. An unauthenticated attacker with a public survey link may bypass lookup protections and access response data, including hidden fields.",
  "mitigation": "Restrict or remove public survey links and block unauthenticated access to result-lookup functionality where possible. Require authorization before exposing lookup configuration or response data, and monitor for a vendor update.",
  "vendor": "javahuang",
  "product": "SurveyKing",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.13.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "SurveyKing",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.539733416666667,
  "t0_at": "2026-11-13T17:22:06.088000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T17:22:06.088000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T17:22:06.088000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-129151"
    }
  }
}

published 2026-11-13 18:16Z
last change 2026-11-14 02:58Z

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.