Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2019-13956: Arbitrary PHP Code Execution via Language Cookie in Discuz!ML 3.2-3.4

Published Jul 18, 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
EPSS4.6%92nd percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Codersclub
IdentifiersCVE-2019-13956CWE-94 · Improper Control of Generation of…

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.

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 allows remote attackers to execute arbitrary PHP code on the server, leading to full compromise of the affected application and potentially the underlying server. Attackers can gain unauthorized access, exfiltrate data, or use the server as a pivot point for further attacks.

Mitigation

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

As an immediate mitigation, implement strict input validation and sanitization on the language cookie value. Deploy web application firewalls (WAF) to detect and block malicious payloads in cookies. Disable or restrict the use of dynamic code execution functions in the application configuration if possible.

Remediation

Patch, then assume compromise.

Upgrade Discuz!ML to a version where this vulnerability is patched. Ensure that all user-supplied input, especially cookies, are properly sanitized and validated before being used in any code execution or inclusion context. Avoid using dynamic code execution functions such as eval or include with user-controlled data.

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
CodersclubDiscuz!Mlapplication
FAQ

Frequently asked questions

Is CVE-2019-13956 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-13956?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2019-13956.
Is there a patch for CVE-2019-13956?
Upgrade Discuz!ML to a version where this vulnerability is patched. Ensure that all user-supplied input, especially cookies, are properly sanitized and validated before being used in any code execution or inclusion context.
What products are affected by CVE-2019-13956?
Codersclub Discuz!Ml.
How severe is CVE-2019-13956?
CVE-2019-13956 has a CVSS v3 score of 9.8 (Critical) and an EPSS score of 4.6% (92nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
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 malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.