CVE-2026-105701

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

GHSA-vjvq-84hj-h4xh ↗EUVD-2026-92986 ↗

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.
Mauro Cassani ACPT (Premium) <= 2.0.66
CWE-434 Unrestricted Upload of File with Dangerous Type
ETK-2026-739, permanent identifier
15d 07h 31msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h40m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

ACPT (Premium) for WordPress through version 2.0.66 has an authorization flaw in its REST form-creation functionality and unsafe email-template rendering. An authenticated user with subscriber-level access or higher may be able to run code on the WordPress server.

mitigation

Disable the affected plugin, or restrict access to its form-creation REST endpoint, until a vendor update is available. Review and remove unnecessary subscriber accounts and other low-privilege logins.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.55%44th percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 06:42Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-06 06:42Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-739",
  "cve_id": "CVE-2026-105701",
  "display_id": "CVE-2026-105701",
  "ghsa_id": "GHSA-vjvq-84hj-h4xh",
  "euvd_id": "EUVD-2026-92986",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper REST authorization and code execution in ACPT (Premium)",
  "summary": "ACPT (Premium) for WordPress through version 2.0.66 has an authorization flaw in its REST form-creation functionality and unsafe email-template rendering. An authenticated user with subscriber-level access or higher may be able to run code on the WordPress server.",
  "mitigation": "Disable the affected plugin, or restrict access to its form-creation REST endpoint, until a vendor update is available. Review and remove unnecessary subscriber accounts and other low-privilege logins.",
  "vendor": "Mauro Cassani",
  "product": "ACPT (Premium)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.0.66"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "ACPT (Premium)",
      "purl": null
    }
  ],
  "cwes": [
    434
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0055,
  "epss_percentile": 0.4496,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.187564083333335,
  "t0_at": "2026-10-06T06:42:03.471000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T06:42:03.471000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T06:42:03.471000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105701"
    }
  }
}

published 2026-10-06 07:01Z
last change 2026-10-21 18:33Z

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.