CVE-2026-110002
waiting for further signalsZero needs more public information before it can validate it.description
Snazzy Social Media Feed for WordPress versions through 2.5 is affected by an arbitrary file-upload vulnerability. An unauthenticated remote attacker may write executable content into a web-accessible cache file, potentially resulting in code execution, because a standalone cache handler is reachable without WordPress authentication or request validation.
mitigation
Disable and remove Snazzy Social Media Feed until a vendor-fixed release is available. Restrict web access to its standalone cache handler and prevent the plugin cache directory from executing PHP as a temporary exposure reduction.
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.
- 2026-10-14 02:27Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-110002
{ "etk_id": "ETK-2026-1533", "cve_id": "CVE-2026-110002", "display_id": "CVE-2026-110002", "ghsa_id": null, "euvd_id": "EUVD-2026-100775", "status": "published", "anchor_state": "anchored", "title": "Arbitrary file upload in Snazzy Social Media Feed", "summary": "Snazzy Social Media Feed for WordPress versions through 2.5 is affected by an arbitrary file-upload vulnerability. An unauthenticated remote attacker may write executable content into a web-accessible cache file, potentially resulting in code execution, because a standalone cache handler is reachable without WordPress authentication or request validation.", "mitigation": "Disable and remove Snazzy Social Media Feed until a vendor-fixed release is available. Restrict web access to its standalone cache handler and prevent the plugin cache directory from executing PHP as a temporary exposure reduction.", "vendor": "snazzyplugins", "product": "Snazzy Social Media Feed", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 2.5" ], "ecosystem": null, "fixed_versions": [], "package_name": "Snazzy Social Media Feed", "purl": null } ], "cwes": [ 434 ], "cvss_score": 9.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": 0.0098, "epss_percentile": 0.6155, "epss_asof": "2026-10-20", "automation": "deterministic", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 75.22386238333333, "t0_at": "2026-10-14T02:27:37.390000+00:00", "signals": { "trigger_signal": { "at": "2026-10-14T02:27:37.390000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-14T02:27:37.390000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-110002" } } }
published 2026-10-14 03:44Z
last change 2026-10-21 04: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.