Skip to main content

Super Video Player EUVDEUVD-2026-96374

| CVE-2026-62044 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-10-10 Patchstack GHSA-hqm5-6vj2-27hv
7.2
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as high-privilege user
  2. Delivery
    Submit crafted serialized payload
  3. Exploit
    Trigger unsafe deserialization (CWE-502)
  4. Execution
    Instantiate malicious object via gadget chain
  5. Impact
    Achieve full C/I/A impact on site

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated session with high privileges (CVSS PR:H - in a WordPress plugin context this typically means administrator-level access) and the ability to submit untrusted serialized data to the Super Video Player plugin feature that performs PHP deserialization. Practical impact beyond object injection is further limited by the need for a usable POP gadget chain in WordPress core, this plugin, or other installed components. Limiting factors: the high privilege prerequisite excludes anonymous and low-privilege users, no user interaction is needed (UI:N), and only installations running Super Video Player version 1.8.13 or earlier are affected.

Impact

The input CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, score 7.2) describes a network-reachable, low-complexity PHP Object Injection with full confidentiality, integrity, and availability impact, but gated behind PR:H - high privileges. In the WordPress plugin context this typically means an administrator (or equivalent high-privilege authenticated user) is required to reach the vulnerable deserialization path, which sharply reduces real-world risk: an attacker already holding admin rights on a WordPress site has substantial control regardless of this flaw. No EPSS score was provided, no POC is indicated, and the CVE is not in CISA KEV, so there is no exploitation signal (no public exploit identified at time of analysis). The dominant risk driver is the CWE-502 deserialization primitive, which, if a usable POP (property-oriented programming) gadget chain exists in WordPress core or co-installed plugins/themes, can escalate to remote code execution - but exploitability of object injection is entirely gadget-dependent and unconfirmed here. Net assessment: a genuine but not urgent issue - meaningful for defense-in-depth and against privilege-abuse/compromised-admin scenarios, not a mass-exploitation priority. Conflict to note: the high PR requirement makes the 'network unauthenticated attacker' framing inapplicable; this is an authenticated, privileged-access flaw despite AV:N.

Exploit ScenarioDerived

An authenticated high-privilege user (per CVSS PR:H, typically an administrator) submits crafted serialized input to a plugin feature that deserializes untrusted data, triggering PHP Object Injection. If a suitable gadget chain is present in the WordPress stack, this can be leveraged for arbitrary object instantiation leading to data disclosure, tampering, or potential code execution. No public proof-of-concept is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 10, 2026

PHP object injection in the bPlugins Super Video Player WordPress plugin affects all versions through 1.8.13, allowing an authenticated high-privilege user to submit untrusted serialized data that the plugin passes to PHP's deserialization routines. Because the CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (7.2), the weakness is network-reachable and low-complexity but gated behind an administrator-level session in the affected WordPress installation, so anonymous and low-privilege visitors cannot reach the vulnerable path; no public exploit identified at time of analysis, and practical impact depends on the presence of a usable POP gadget chain in WordPress core, the plugin itself, or other installed components.

RemediationAI

No vendor-released patch version is identified in the available input data - the advisory describes the issue as affecting Super Video Player through 1.8.13 but does not name a fixed release, so administrators should check the Patchstack record (https://patchstack.com/database/wordpress/plugin/super-video-player/vulnerability/wordpress-super-video-player-plugin-1-8-13-php-object-injection-vulnerability?_s_id=cve) and the plugin's WordPress.org page for a version newer than 1.8.13 and upgrade as soon as one is published, verifying plugin compatibility afterwards since a major version bump can change shortcode or player behavior. Until a fix is confirmed, the highest-value compensating control is removing the prerequisite privilege: audit administrator and editor accounts, enforce least privilege and strong unique credentials plus multi-factor authentication on all high-privilege users, since PR:H means only such accounts can reach the vulnerable deserialization path. If the plugin is not in active use, deactivate and delete it outright, which eliminates the exposure with no functional trade-off; if it must stay active, restrict wp-admin and admin-ajax.php access by IP or VPN and block untrusted serialized payloads (the classic O:<length>:"ClassName" pattern) at the WAF or reverse proxy - noting that generic serialization filters may break legitimate plugin/theme functionality and require tuning. General WordPress hardening (keeping core, themes, and other plugins patched to limit usable POP gadget chains, and monitoring for unexpected option or post changes) reduces but does not remove the risk, and none of these workarounds fully substitutes for an upstream fix once it becomes available.

Affected VersionsENISA

Super Video Player 0 ≤1.8.13

Affected Packages

euvd super_video_player no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is CWE-502 (Deserialization of Untrusted Data), the classic PHP Object Injection class that arises when attacker-supplied input reaches unserialize() - typically through a plugin option, AJAX handler, shortcode attribute, or REST parameter that the Super Video Player plugin stores or forwards without validation. On deserialization, PHP reconstructs arbitrary objects and automatically invokes magic methods such as __wakeup(), __destruct(), and __toString(); if a property-oriented programming (POP) gadget chain exists among the loaded classes, an attacker can pivot from mere object creation to file operations, SQL execution, or further code execution. The affected component is identified by CPE cpe:2.3:a:bplugins:super_video_player:*:*:*:*:*:*:*:* and is reported through Patchstack as a WordPress plugin vulnerability, so the deployed stack is WordPress with the Super Video Player extension; the underlying protocol surface is HTTP(S) via the plugin's own request handlers rather than WordPress core. Exploitability beyond object instantiation is constrained by the availability of a viable gadget chain, and the PR:H rating means the attacker must already hold a high-privilege account - in the WordPress context normally an administrator - which substantially narrows the realistic threat model to privilege escalation, persistence, or site takeover by a compromised or malicious admin rather than pre-authentication compromise.

Know when Super Video Player gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.2 HIGH

Deserialization is reachable over the network (AV:N) with low complexity but requires an admin-level authenticated user (PR:H); object injection can fully compromise site C/I/A.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Deserialization of Untrusted Data vulnerability in bPlugins Super Video Player super-video-player allows Object Injection.This issue affects Super Video Player: from n/a through 1.8.13.

Executive ViewAI

Why It Matters

All versions of the bPlugins Super Video Player WordPress plugin up to and including 1.8.13 contain a PHP object injection flaw that lets an attacker with an existing administrator-level session on the site submit crafted serialized data into the plugin's deserialization path. There is no vendor patch at this time, and while exploitation requires an already-privileged account plus a usable gadget chain among the site's installed code, a successful attack could give that actor full read/write/execute reach across the WordPress installation and its hosted content. Leadership should care because any group running this plugin on internet-facing WordPress sites - marketing, corporate web properties, or shared hosting environments - cannot remediate through normal patching and must rely on compensating controls and account-hygiene measures.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the bPlugins Super Video Player plugin (all versions through 1.8.13) where feasible; strictly limit and audit WordPress administrator accounts, enforce MFA, and rotate credentials; apply virtual patching or WAF rules that block serialized PHP object payloads to the plugin's endpoints; reduce the available PHP object injection gadget surface by removing unused plugins and themes; and monitor web server, WordPress, and PHP logs for anomalous deserialization activity and unexpected administrative changes.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Low
niche single-purpose WordPress video-player plugin, limited install base
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy