Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2016-1209: PHP Object Injection in Ninja Forms <2.9.42.1

Published May 14, 2016 · 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
EPSS61.6%99th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Ninjaforms
IdentifiersCVE-2016-1209CWE-502

A vulnerability in Ninja Forms plugin for WordPress prior to version 2.9.42.1 allows remote attackers to perform PHP object injection by sending crafted serialized values in a POST request. The vulnerable code deserializes user-supplied input without proper validation, enabling attackers to instantiate arbitrary PHP objects.

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 lead to arbitrary code execution, data manipulation, or other attacks depending on the available PHP classes and application context. Attackers may leverage this to compromise the WordPress site or escalate privileges.

Mitigation

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

If immediate upgrade is not possible, block or sanitize serialized input in POST requests to Ninja Forms endpoints, and restrict access to the plugin's endpoints using web application firewall rules.

Remediation

Patch, then assume compromise.

Upgrade Ninja Forms to version 2.9.42.1 or later, where the deserialization vulnerability is patched.

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
NinjaformsNinja Formsapplication
FAQ

Frequently asked questions

Is CVE-2016-1209 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2016-1209 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2016-1209?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2016-1209, the earliest disclosed May 4, 2016.
Is there a patch for CVE-2016-1209?
Upgrade Ninja Forms to version 2.9.42.1 or later, where the deserialization vulnerability is patched.
What products are affected by CVE-2016-1209?
Ninjaforms Ninja Forms.
How severe is CVE-2016-1209?
CVE-2016-1209 has a CVSS v3 score of 9.8 (Critical) and an EPSS score of 61.6% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

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 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.