CVE-2026-121787

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

GHSA-2fg2-6v8g-5wgr ↗EUVD-2026-126179 ↗

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.
Social Viral Downloader <= 2.0.3
CWE-862 Missing Authorization
ETK-2026-4569Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 14h 20msince last run
1h 18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h46m
0
+4h
+6h
+8h
+10h
+12h

description

Social Viral Downloader for WordPress through version 2.0.3 is affected by missing authorization and nonce checks on a download-log deletion action. An unauthenticated attacker could delete the plugin's entire download log if the vulnerable plugin is accessible.

mitigation

Disable or remove Social Viral Downloader until an updated release is available. Restrict unauthenticated access to the affected WordPress site or plugin endpoints to reduce exposure.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.18%7th percentile
agent run time
1h 18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-16 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-16 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4569",
  "cve_id": "CVE-2026-121787",
  "display_id": "CVE-2026-121787",
  "ghsa_id": "GHSA-2fg2-6v8g-5wgr",
  "euvd_id": "EUVD-2026-126179",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated download log deletion in Social Viral Downloader",
  "summary": "Social Viral Downloader for WordPress through version 2.0.3 is affected by missing authorization and nonce checks on a download-log deletion action. An unauthenticated attacker could delete the plugin's entire download log if the vulnerable plugin is accessible.",
  "mitigation": "Disable or remove Social Viral Downloader until an updated release is available. Restrict unauthenticated access to the affected WordPress site or plugin endpoints to reduce exposure.",
  "vendor": null,
  "product": "Social Viral Downloader",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.0.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Social Viral Downloader",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 5.3,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
  "epss_score": 0.0018,
  "epss_percentile": 0.0782,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 77.98711491666667,
  "t0_at": "2026-11-16T06:00:05.765000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-16T06:00:05.765000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-16T06:00:05.765000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-121787"
    }
  }
}

published 2026-11-16 06:28Z
last change 2026-11-18 21: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.