CVE-2026-66570
validatedZero produced an exploit or a check.GHSA-9jg4-gr2w-m5jg ↗EUVD-2026-114863 ↗
description
WordPress File Upload (wp-file-upload) through version 5.2.1 is affected by a stored cross-site scripting vulnerability. An attacker may cause script content to execute in another user's browser when that user views affected content; the advisory indicates user interaction is required.
mitigation
Update or disable wp-file-upload, as no fixed version is recorded in the advisory. Until an update is available, restrict access to upload and content-management functions and review stored plugin content for untrusted markup.
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-11-01 16:00Zcve_org: trigger signal, started the run
- 2026-11-01 16:11Z
this entry in the feed
GET /api/v1/feed/CVE-2026-66570
{ "etk_id": "ETK-2026-3236", "cve_id": "CVE-2026-66570", "display_id": "CVE-2026-66570", "ghsa_id": "GHSA-9jg4-gr2w-m5jg", "euvd_id": "EUVD-2026-114863", "status": "published", "anchor_state": "anchored", "title": "Stored cross-site scripting in wp-file-upload", "summary": "WordPress File Upload (wp-file-upload) through version 5.2.1 is affected by a stored cross-site scripting vulnerability. An attacker may cause script content to execute in another user's browser when that user views affected content; the advisory indicates user interaction is required.", "mitigation": "Update or disable wp-file-upload, as no fixed version is recorded in the advisory. Until an update is available, restrict access to upload and content-management functions and review stored plugin content for untrusted markup.", "vendor": "Nickboss", "product": "WordPress File Upload", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 5.2.1" ], "ecosystem": null, "fixed_versions": [], "package_name": "wp-file-upload", "purl": null } ], "cwes": [ 79 ], "cvss_score": 7.1, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": true, "check_confidence_basis": "upstream", "exploit": false, "pipeline_minutes": 0.0485343, "t0_at": "2026-11-01T16:00:09.605000+00:00", "signals": { "check": { "at": "2026-11-01T16:11:10.291913+00:00", "days": 0.007646839270833333, "is_lower_bound": false, "measured_at": "2026-11-01T16:00:09.605000+00:00", "url": null }, "trigger_signal": { "at": "2026-11-01T16:00:09.605000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-01T16:00:09.605000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-66570" } } }
published 2026-11-01 16:11Z
last change 2026-11-01 18:43Z
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.