CVE-2026-111832
validatedZero produced an exploit or a check.GHSA-2hrr-86cg-w5v9 ↗EUVD-2026-107282 ↗
description
WP Mailster versions through 1.9.1.0 are affected by unrestricted upload of dangerous file types. An unauthenticated remote attacker may upload a file that can lead to execution of code on the web server, provided the vulnerable upload functionality is reachable.
mitigation
Deactivate or remove WP Mailster until a vendor-fixed release is available. Restrict access to the affected upload functionality and ensure the web server does not execute files from upload directories as defense in depth.
outcome
Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-21 14:00Zcve_org: trigger signal, started the run
- 2026-10-21 14:31Z
this entry in the feed
GET /api/v1/feed/CVE-2026-111832
{ "etk_id": "ETK-2026-2324", "cve_id": "CVE-2026-111832", "display_id": "CVE-2026-111832", "ghsa_id": "GHSA-2hrr-86cg-w5v9", "euvd_id": "EUVD-2026-107282", "status": "published", "anchor_state": "anchored", "title": "Unrestricted dangerous file upload in WP Mailster", "summary": "WP Mailster versions through 1.9.1.0 are affected by unrestricted upload of dangerous file types. An unauthenticated remote attacker may upload a file that can lead to execution of code on the web server, provided the vulnerable upload functionality is reachable.", "mitigation": "Deactivate or remove WP Mailster until a vendor-fixed release is available. Restrict access to the affected upload functionality and ensure the web server does not execute files from upload directories as defense in depth.", "vendor": "WP Mailster", "product": "WP Mailster", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 1.9.1.0" ], "ecosystem": null, "fixed_versions": [], "package_name": "wp-mailster", "purl": null } ], "cwes": [ 434 ], "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": "deterministic", "check": true, "check_confidence_basis": "upstream", "exploit": false, "pipeline_minutes": 0.013143266666666667, "t0_at": "2026-10-21T14:00:13.392000+00:00", "signals": { "check": { "at": "2026-10-21T14:31:53.889961+00:00", "days": 0.02199650417824074, "is_lower_bound": false, "measured_at": "2026-10-21T14:00:13.392000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-21T14:00:13.392000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-21T14:00:13.392000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-111832" } } }
published 2026-10-21 14:31Z
last change 2026-10-21 16:15Z
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.