Unauthenticated PHP object injection via file field
Published Jul 13, 2026 · Updated Jul 13, 2026
PHP object injection in CRM Perks Contact Form Entries before 1.5.2 allows remote attackers to plant objects through a form field. The entry editor passes the stored file-field value to maybe_unserialize without restricting permitted PHP classes, instantiating the supplied object. Exploitation requires a published form with a file-upload field, an administrator to save the stored entry, and a usable gadget class from installed code; the resulting action is limited to that gadget.
Summary
What happened
PHP object injection in CRM Perks Contact Form Entries before 1.5.2 allows remote attackers to plant objects through a form field. The entry editor passes the stored file-field value to maybe_unserialize without restricting permitted PHP classes, instantiating the supplied object. Exploitation requires a published form with a file-upload field, an administrator to save the stored entry, and a usable gadget class from installed code; the resulting action is limited to that gadget.
The record
- CVE
- CVE-2026-12081
- Published
- Jul 13, 2026
- Updated
- Jul 13, 2026
- Vendor
- CRM Perks
- Product
- Contact Form Entries
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2026CVE publishedPublication date reported by the CVE source.
- Jul 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.5.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan entry file-field object-injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo