Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2019-5129: Unauthenticated Command Injection in YouPHPTube Encoder 2.3

Published Oct 25, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS38.5%99th percentile
CISA KEVNoNot listed
In the wildReported566 exploitation records in Mallory
Vendor
Youphptube
IdentifiersCVE-2019-5129CWE-78 · Improper Neutralization of Special…

CVE-2019-5129 is a command injection vulnerability in YouPHPTube Encoder 2.3, a plugin that provides encoder functionality for YouPHPTube. The vulnerable input is the base64Url parameter handled by /objects/getSpiritsFromVideo.php. An attacker can supply crafted input to this parameter and trigger execution of unintended operating system commands on the server. The issue is described as exploitable without authentication.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an unauthenticated attacker to compromise the server hosting the YouPHPTube Encoder component. Because the flaw is a command injection in a server-side PHP endpoint, impact can include arbitrary command execution in the security context of the web application, which may lead to full system compromise depending on host configuration and privileges.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict or disable access to /objects/getSpiritsFromVideo.php, especially from untrusted networks. Place the encoder component behind authentication or network ACLs where feasible, use a WAF to block command-injection metacharacters and anomalous requests targeting base64Url, and run the web application with minimal OS privileges in an isolated environment to reduce post-exploitation impact. Monitoring for suspicious child-process execution from the web server or PHP runtime is also advisable.

Remediation

Patch, then assume compromise.

Upgrade YouPHPTube Encoder to a version in which the base64Url parameter in /objects/getSpiritsFromVideo.php is properly sanitized or no longer passed to shell execution in an unsafe manner. The vulnerable code path should be corrected to avoid invoking OS commands with untrusted input, preferably by removing shell usage entirely or by using strict allowlisting and safe APIs. If a vendor-fixed release is available, apply it promptly.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
YouphptubeYouphptube Encoderapplication
FAQ

Frequently asked questions

Is CVE-2019-5129 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2019-5129?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2019-5129.
Is there a patch for CVE-2019-5129?
Upgrade YouPHPTube Encoder to a version in which the base64Url parameter in /objects/getSpiritsFromVideo.php is properly sanitized or no longer passed to shell execution in an unsafe manner. The vulnerable code path should be corrected to avoid invoking OS commands with untrusted input, preferably by removing shell usage entirely or by using strict allowlisting and safe APIs.
What products are affected by CVE-2019-5129?
Youphptube Encoder.
How severe is CVE-2019-5129?
CVE-2019-5129 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 38.5% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.