CVE-2026-75807

validatedZero produced an exploit or a check.

GHSA-2pfc-9h54-m36f ↗EUVD-2026-68133 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.+67d
cyberlord92 SAML Single Sign On – SSO Login <= 5.4.6
ETK-2026-3513Zero's internal tracking ID, independent of the CVE number., permanent identifier
+67dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−66dtrigger signal +0dcheck available+0.6dkev+1.0dagent stopped
−60d
−40d
−20d

description

SAML Single Sign On – SSO Login for WordPress through version 5.4.6 is affected by an authentication-bypass issue. An unauthenticated attacker may be able to alter the plugin's trusted identity-provider certificate and then sign in as arbitrary WordPress users; exploitation depends on an administrator performing a repair after a SAML configuration-test error.

mitigation

No fixed version is recorded; disable the plugin or prevent untrusted access to its SAML assertion-processing endpoint until a corrected release is available. Avoid performing the described repair action after a configuration-test error, and verify the configured identity-provider certificate and active privileged sessions.

check
available
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.
deterministic
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
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-08-29 17:25Z
Δ 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.
+67d

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-08-29 17:25Z
  2. 2026-11-04
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-04 00:00Z
  4. 2026-11-04 15:05Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3513",
  "cve_id": "CVE-2026-75807",
  "display_id": "CVE-2026-75807",
  "ghsa_id": "GHSA-2pfc-9h54-m36f",
  "euvd_id": "EUVD-2026-68133",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in SAML Single Sign On – SSO Login",
  "summary": "SAML Single Sign On – SSO Login for WordPress through version 5.4.6 is affected by an authentication-bypass issue. An unauthenticated attacker may be able to alter the plugin's trusted identity-provider certificate and then sign in as arbitrary WordPress users; exploitation depends on an administrator performing a repair after a SAML configuration-test error.",
  "mitigation": "No fixed version is recorded; disable the plugin or prevent untrusted access to its SAML assertion-processing endpoint until a corrected release is available. Avoid performing the described repair action after a configuration-test error, and verify the configured identity-provider certificate and active privileged sessions.",
  "vendor": "cyberlord92",
  "product": "SAML Single Sign On – SSO Login",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 5.4.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "SAML Single Sign On – SSO Login",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.01691945,
  "t0_at": "2026-08-29T17:25:48.408000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-04T15:05:42.711536+00:00",
      "days": 66.90271184648148,
      "is_lower_bound": false,
      "measured_at": "2026-08-29T17:25:48.408000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-11-04T00:00:00+00:00",
      "days": 67,
      "is_lower_bound": false,
      "measured_at": "2026-08-29T17:25:48.408000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-75807"
    },
    "trigger_signal": {
      "at": "2026-11-04T00:00:00+00:00",
      "days": 66.27374527777778,
      "is_lower_bound": false,
      "measured_at": "2026-08-29T17:25:48.408000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-75807"
    }
  }
}

published 2026-11-04 15:05Z
last change 2026-11-04 16:15Z

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.