Skip to main content
CVE-2025-64325VulnerabilityPublished

CVE-2025-64325: EmbySupport Emby.Security · Cross-site Scripting

Affects EmbySupport Emby.SecuritySource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High : upgrade to 4.8.1.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.8.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade embysupport/Emby.Security to 4.8.1.0.

Affected software

ProductAffectedFixed in
GitHubembysupport/Emby.Securitypkg:github/embysupport/Emby.SecurityOther threatsAffected
  • <4.8.1.0
Fixed in
  • 4.8.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately upgrade all Emby Server instances to version 4.8.1.0 or later, or Beta 4.9.0.0-beta or later, where the vulnerability is patched. 2. Restrict access to the admin dashboard to trusted networks and users only, using network segmentation and firewall rules to limit exposure. 3. Implement web application firewall (WAF) rules that detect and block suspicious X-Emby-Client header values or unusual device registration patterns. 4. Educate administrators about the risk of interacting with untrusted device entries and encourage cautious behavior when reviewing device lists. 5. Monitor server logs for unusual authentication requests or device additions that could indicate exploitation attempts. 6. Consider deploying Content Security Policy (CSP) headers to reduce the impact of potential XSS attacks by restricting script execution sources. 7. Regularly audit and review user privileges to ensure minimal necessary access is granted, reducing the risk from compromised accounts. 8. Maintain up-to-date backups of server configurations and media content to enable recovery in case of compromise.

Description

Emby Server is a personal media server. Prior to version 4.8.1.0 and prior to Beta version 4.9.0.0-beta, a malicious user can send an authentication request with a manipulated X-Emby-Client value, which gets added to the devices section of the admin dashboard without sanitization. This issue has been patched in version 4.8.1.0 and Beta version 4.9.0.0-beta.

References

Community reviews

Loading reviews…