CVE-2026-105413

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

EUVD-2026-116712 ↗

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.
Form Maker by 10Web < 1.15.51
fixed in 1.15.51
ETK-2026-3462Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 01msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h07m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Form Maker by 10Web releases before 1.15.51 can render submitted form data unsafely in the administration interface. An unauthenticated attacker may cause script execution in an administrator's browser if they can submit a form and an administrator later opens that submission.

mitigation

Update Form Maker by 10Web to version 1.15.51 or later. Until updated, restrict public form submissions where possible and avoid opening untrusted submissions in the administrative interface.

fixed in 1.15.51

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.
–
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
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-04 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3462",
  "cve_id": "CVE-2026-105413",
  "display_id": "CVE-2026-105413",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-116712",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in Form Maker WordPress plugin",
  "summary": "Form Maker by 10Web releases before 1.15.51 can render submitted form data unsafely in the administration interface. An unauthenticated attacker may cause script execution in an administrator's browser if they can submit a form and an administrator later opens that submission.",
  "mitigation": "Update Form Maker by 10Web to version 1.15.51 or later. Until updated, restrict public form submissions where possible and avoid opening untrusted submissions in the administrative interface.",
  "vendor": null,
  "product": "Form Maker by 10Web",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.15.51"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.15.51"
      ],
      "package_name": "Form Maker by 10Web",
      "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": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 26.05140235,
  "t0_at": "2026-11-04T06:00:24.194000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T06:00:24.194000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T06:00:24.194000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105413"
    }
  }
}

published 2026-11-04 06:41Z
last change 2026-11-04 09:41Z

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.