CVE-2026-113615

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

GHSA-rgfv-fwf2-4544 ↗EUVD-2026-117910 ↗

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.
GS JWT Authentication for WP REST API <= 1.0.0
ETK-2026-3701Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 06msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h32m
0
+4h
+6h
+8h
+10h
+12h

description

GS JWT Authentication for WP REST API for WordPress is affected through version 1.0.0. An unauthenticated attacker may exploit SQL injection in certain REST routes to obtain an administrator session; access to those exposed routes is the relevant precondition.

mitigation

Disable the plugin or restrict unauthenticated access to its REST routes until an updated release is available. Review WordPress administrator sessions and credentials for possible compromise.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-06 06:00Z
Δ 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-06 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-06 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3701",
  "cve_id": "CVE-2026-113615",
  "display_id": "CVE-2026-113615",
  "ghsa_id": "GHSA-rgfv-fwf2-4544",
  "euvd_id": "EUVD-2026-117910",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in GS JWT Authentication for WP REST API",
  "summary": "GS JWT Authentication for WP REST API for WordPress is affected through version 1.0.0. An unauthenticated attacker may exploit SQL injection in certain REST routes to obtain an administrator session; access to those exposed routes is the relevant precondition.",
  "mitigation": "Disable the plugin or restrict unauthenticated access to its REST routes until an updated release is available. Review WordPress administrator sessions and credentials for possible compromise.",
  "vendor": null,
  "product": "GS JWT Authentication for WP REST API",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "GS JWT Authentication for WP REST API",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.96575343333333,
  "t0_at": "2026-11-06T06:00:27.462000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T06:00:27.462000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T06:00:27.462000+00:00",
      "url": "https://github.com/advisories/GHSA-rgfv-fwf2-4544"
    }
  }
}

published 2026-11-06 06:55Z
last change 2026-11-06 08:31Z

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.