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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
/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.Patch, then assume compromise.
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.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.