Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2014-2921: PHP Object Injection in Pimcore Newsletter getObjectByToken

Published Apr 21, 2014 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS6.4%94th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Pimcore
IdentifiersCVE-2014-2921CWE-502

The getObjectByToken function in Newsletter.php within the Pimcore_Tool_Newsletter module (versions 1.4.9 through 2.0.0) is vulnerable to PHP object injection. The vulnerability arises from improper handling of objects obtained by unserializing Lucene search data, allowing remote attackers to inject arbitrary PHP objects. Specifically, exploitation can occur via a crafted Zend_Pdf_ElementFactory_Proxy object and a pathname containing a trailing null byte (\0), leading to arbitrary code execution.

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, potentially leading to full compromise of the affected system. Attackers can leverage this to gain unauthorized access, escalate privileges, or further pivot within the environment.

Mitigation

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

Restrict access to the vulnerable functionality to trusted users only. Employ web application firewalls (WAFs) to detect and block malicious payloads targeting unserialize operations. Monitor for suspicious activity and review code for unsafe use of unserialize.

Remediation

Patch, then assume compromise.

Upgrade Pimcore to a version later than 2.0.0 where this vulnerability is patched. Ensure that all unserialize operations are performed on trusted data only, and consider using safer serialization mechanisms or input validation to prevent object injection.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
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
PimcorePimcoreapplication
FAQ

Frequently asked questions

Is CVE-2014-2921 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2014-2921 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2014-2921?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2014-2921.
Is there a patch for CVE-2014-2921?
Upgrade Pimcore to a version later than 2.0.0 where this vulnerability is patched. Ensure that all unserialize operations are performed on trusted data only, and consider using safer serialization mechanisms or input validation to prevent object injection.
What products are affected by CVE-2014-2921?
Pimcore.
How severe is CVE-2014-2921?
CVE-2014-2921 has a CVSS v2 score of 7.5 (High) and an EPSS score of 6.4% (94th 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.