CVE-2026-108687

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

GHSA-6883-p7cr-883r ↗EUVD-2026-129476 ↗

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.
SAML SSO Login <= 1.5.2
ETK-2026-4887Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 10msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h51m
0
+4h
+6h
+8h
+10h
+12h

description

SAML SSO Login for WordPress, through version 1.5.2, can bind identity data to a different assertion than the one whose signature is checked. An attacker with a legitimately signed SAML assertion may be able to sign in as an existing user, potentially including an administrator; access to such an assertion is required.

mitigation

Disable the plugin's SAML-based login path until a corrected release is available. Restrict and monitor SAML authentication, especially for administrative accounts, to reduce exposure.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 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

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-19 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4887",
  "cve_id": "CVE-2026-108687",
  "display_id": "CVE-2026-108687",
  "ghsa_id": "GHSA-6883-p7cr-883r",
  "euvd_id": "EUVD-2026-129476",
  "status": "published",
  "anchor_state": "anchored",
  "title": "XML signature wrapping in SAML SSO Login",
  "summary": "SAML SSO Login for WordPress, through version 1.5.2, can bind identity data to a different assertion than the one whose signature is checked. An attacker with a legitimately signed SAML assertion may be able to sign in as an existing user, potentially including an administrator; access to such an assertion is required.",
  "mitigation": "Disable the plugin's SAML-based login path until a corrected release is available. Restrict and monitor SAML authentication, especially for administrative accounts, to reduce exposure.",
  "vendor": null,
  "product": "SAML SSO Login",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.5.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "SAML SSO Login",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.098466333333334,
  "t0_at": "2026-11-19T06:00:06.297000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-19T06:00:06.297000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T06:00:06.297000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108687"
    }
  }
}

published 2026-11-19 06:26Z
last change 2026-11-19 17:22Z

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.