Loading vulnerability…
Discuz!ML versions 3.2 through 3.4 are vulnerable to arbitrary PHP code execution due to improper handling of the language cookie. An attacker can modify the language cookie value to inject and execute arbitrary PHP code on the server. For example, by setting the cookie 4gH4_0df5_language to a value such as en'.phpinfo().';, the attacker can trigger execution of the phpinfo() function, demonstrating code execution. The vulnerability is due to insufficient sanitization of user-supplied input in the language cookie, which is used in a PHP eval context or similar dynamic code inclusion.
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 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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.