CVE-2026-106015

validatingZero is analyzing and reversing it now.

GHSA-xxh9-x8mr-vqr4 ↗EUVD-2026-119475 ↗

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.
Ecommerce Affiliate <= 1.0.0
ETK-2026-3883Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Ecommerce Affiliate for WordPress through version 1.0.0 has insufficient controls around one-time-password issuance and verification. An unauthenticated attacker may take over user accounts, including administrator accounts, because OTP operations are not adequately associated with the intended account and verification attempts are not limited.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Disable or remove the affected plugin until you can confirm that a vendor update corrects the OTP ownership and attempt-limiting controls. Restrict access to WordPress authentication functions and review accounts for unauthorized changes.

check
building now
exploit
not yet
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
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 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

Run in progress: no artifact yet.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3883",
  "cve_id": "CVE-2026-106015",
  "display_id": "CVE-2026-106015",
  "ghsa_id": "GHSA-xxh9-x8mr-vqr4",
  "euvd_id": "EUVD-2026-119475",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "OTP authorization flaws in Ecommerce Affiliate",
  "summary": "Ecommerce Affiliate for WordPress through version 1.0.0 has insufficient controls around one-time-password issuance and verification. An unauthenticated attacker may take over user accounts, including administrator accounts, because OTP operations are not adequately associated with the intended account and verification attempts are not limited.",
  "mitigation": "Disable or remove the affected plugin until you can confirm that a vendor update corrects the OTP ownership and attempt-limiting controls. Restrict access to WordPress authentication functions and review accounts for unauthorized changes.",
  "vendor": null,
  "product": "Ecommerce Affiliate",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Ecommerce Affiliate",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-08T06:00:30.488000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T06:00:30.488000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T06:00:30.488000+00:00",
      "url": "https://github.com/advisories/GHSA-xxh9-x8mr-vqr4"
    }
  }
}

published 2026-11-08 07:02Z
last change 2026-11-08 07:19Z

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.