Ultimate PHP Board (UPB) 1.9 improperly stores attacker-controlled HTTP User-Agent content in an executable PHP-formatted log without neutralizing PHP syntax. An unauthenticated remote attacker can submit a User-Agent containing PHP code; that code is subsequently interpreted when an UPB administrator views the IP-log administration functionality. This is static code injection (CWE-96).
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.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote arbitrary PHP code-execution vulnerability in Ultimate PHP Board (UPB) 1.9. An attacker can place PHP code in an HTTP User-Agent header; the code is executed with UPB administrator privileges when an administrator accesses admin_iplog.php.
A PHP static code-injection vulnerability where attacker-controlled User-Agent header content was inserted into a log file implemented as a PHP script.
A static code-injection vulnerability in which PHP code supplied through an HTTP User-Agent header was directly written into a log file implemented as a PHP script.
PHP code-injection vulnerability in which a User-Agent HTTP header is directly inserted into a log file implemented as a PHP script.
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.