cve.bz

CVE-2026-96652 Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability

5.3 mediumKEVEPSS 12%

Medium (5.3) in Plex Media Server. In CISA KEV since 2026-10-20. EPSS 12% estimated probability of exploitation activity in the next 30 days.

On this page
Plex Media Server before 1.43.3.10861 allows SSRF via '/player/timeline'. An attacker using any X-Plex-Token value can include a full URL in the 'protocol' parameter and force the Plex server to POST to the attacker's chosen destination.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
12% (unchanged from 12% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-10-20, due 2026-11-03
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: partial, assessed 2026-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-96652 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96652?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96652?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-96652 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Plex Media Serverbefore 1.43.3.10861

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • code-zm/plex2shell Harbor Check: matches CVE 109 stars, created
    CVE-2026-96652 CVE-2026-96654 CVE-2026-96655 CVE-2026-96656
  • gmh5225/plex2shell Harbor Check: matches CVE 1 star, created
    CVE-2026-96652 CVE-2026-96654 CVE-2026-96655 CVE-2026-96656
  • basesixtythree/B63-POC-CVE-2026-96652 Harbor Check: matches CVE 0 stars, Python, created
    PoC and verification material for CVE-2026-96652 (Plex Media Server timeline SSRF, owner-token disclosure chain)

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON