CVE-2026-118423

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

EUVD-2026-117971 ↗

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.
WP Libre Form >= 1.5.0.1, <= 1.5.0.1
ETK-2026-3702Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 48msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h29m
+2h
+4h
+6h
+8h
+10h
+12h

description

WP Libre Form 1.5.0.1 does not properly restrict file types submitted through its forms. An unauthenticated attacker may upload server-executable PHP files to a web-accessible location and run code, provided the plugin's upload form is exposed and uploaded files can be served and executed by the web server.

mitigation

Disable WP Libre Form upload forms or restrict public access to them until an updated release is available. Configure the web server to prevent execution of PHP and other scripts in upload directories.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-06 07:30Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-06 07:30Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3702",
  "cve_id": "CVE-2026-118423",
  "display_id": "CVE-2026-118423",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-117971",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated unrestricted file upload in WP Libre Form",
  "summary": "WP Libre Form 1.5.0.1 does not properly restrict file types submitted through its forms. An unauthenticated attacker may upload server-executable PHP files to a web-accessible location and run code, provided the plugin's upload form is exposed and uploaded files can be served and executed by the web server.",
  "mitigation": "Disable WP Libre Form upload forms or restrict public access to them until an updated release is available. Configure the web server to prevent execution of PHP and other scripts in upload directories.",
  "vendor": null,
  "product": "WP Libre Form",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.5.0.1, <= 1.5.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WP Libre Form",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.525117383333333,
  "t0_at": "2026-11-06T07:30:55.270000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T07:30:55.270000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T07:30:55.270000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-118423"
    }
  }
}

published 2026-11-06 07:50Z
last change 2026-11-06 08:45Z

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.