CVE-2026-124976

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

GHSA-4qm6-c87x-2g36 ↗EUVD-2026-132111 ↗

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.
swte Swift Performance Lite <= 2.3.7.5
ETK-2026-5142Zero's internal tracking ID, independent of the CVE number., permanent identifier
8h 45msince 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+2h42m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Swift Performance Lite for WordPress through version 2.3.7.5 is affected by stored cross-site scripting. An unauthenticated attacker may cause script content to be retained and run in visitors' browsers when AJAX Cache includes a configured Cacheable AJAX Action.

mitigation

Disable AJAX Cache or remove every Cacheable AJAX Action configuration until an updated release is installed. Monitor for and promptly apply a vendor release that addresses the issue.

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-21 11: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

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-21 11:30Z
    ghsa: trigger signal, started the run
  2. 2026-11-21 11:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-5142",
  "cve_id": "CVE-2026-124976",
  "display_id": "CVE-2026-124976",
  "ghsa_id": "GHSA-4qm6-c87x-2g36",
  "euvd_id": "EUVD-2026-132111",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in Swift Performance Lite",
  "summary": "Swift Performance Lite for WordPress through version 2.3.7.5 is affected by stored cross-site scripting. An unauthenticated attacker may cause script content to be retained and run in visitors' browsers when AJAX Cache includes a configured Cacheable AJAX Action.",
  "mitigation": "Disable AJAX Cache or remove every Cacheable AJAX Action configuration until an updated release is installed. Monitor for and promptly apply a vendor release that addresses the issue.",
  "vendor": "swte",
  "product": "Swift Performance Lite",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.3.7.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Swift Performance Lite",
      "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.410290083333333,
  "t0_at": "2026-11-21T11:30:56.537000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-21T11:30:56.537000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-21T11:30:56.537000+00:00",
      "url": "https://github.com/advisories/GHSA-4qm6-c87x-2g36"
    }
  }
}

published 2026-11-21 13:55Z
last change 2026-11-21 22:40Z

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.