CVE-2026-126040

validatedZero produced an exploit or a check.

GHSA-688g-qg2p-7c63 ↗EUVD-2026-128449 ↗

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.
Hide My WP Ghost >= 7.0.00, < 7.0.19
fixed in 7.0.19
ETK-2026-4767Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1h57mTTV
31mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+1h57magent stopped
0
+1h

description

Hide My WP Ghost for WordPress versions before 7.0.19 do not apply two-factor authentication to every authentication path. An attacker with a valid user password may be able to sign in as that user without completing the second factor.

mitigation

Upgrade Hide My WP Ghost to version 7.0.19 or later. Reset potentially exposed passwords and review account authentication activity.

fixed in 7.0.19

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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-11-18 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-18 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4767",
  "cve_id": "CVE-2026-126040",
  "display_id": "CVE-2026-126040",
  "ghsa_id": "GHSA-688g-qg2p-7c63",
  "euvd_id": "EUVD-2026-128449",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Two-factor authentication bypass in Hide My WP Ghost",
  "summary": "Hide My WP Ghost for WordPress versions before 7.0.19 do not apply two-factor authentication to every authentication path. An attacker with a valid user password may be able to sign in as that user without completing the second factor.",
  "mitigation": "Upgrade Hide My WP Ghost to version 7.0.19 or later. Reset potentially exposed passwords and review account authentication activity.",
  "vendor": null,
  "product": "Hide My WP Ghost",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0.00, < 7.0.19"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.0.19"
      ],
      "package_name": "Hide My WP Ghost",
      "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": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 31.214256566666666,
  "t0_at": "2026-11-18T06:00:08.474000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-18T07:57:16.503210+00:00",
      "days": 0.08134293067129629,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T06:00:08.474000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-18T06:00:08.474000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T06:00:08.474000+00:00",
      "url": "https://github.com/advisories/GHSA-688g-qg2p-7c63"
    }
  }
}

published 2026-11-18 07:25Z
last change 2026-11-18 21:43Z

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.