CVE-2026-49105
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated PHP Object Injection in WP Zendesk for Contact Form 7, WPForms, Elementor, Formidable and Ninja Forms <= 1.1.4 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an unauthenticated PHP Object Injection vulnerability in a WordPress plugin that integrates with Contact Form 7, WPForms, Elementor, Formidable, and Ninja Forms. The plugin deserializes untrusted user input without proper sanitization, allowing remote attackers to inject malicious PHP objects and potentially execute arbitrary code via magic methods.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP Zendesk plugin is installedLog in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WP Zendesk' or 'Zendesk' in the list of active and inactive pluginsAffected if WP Zendesk plugin appears in the plugins list regardless of activation status
-
Check installed version of WP Zendesk pluginIn WordPress admin, go to Plugins > Installed Plugins, find WP Zendesk plugin, and note the version number displayed below the plugin nameAffected if Version is 1.1.4 or lower, or if the version cannot be determined (plugin may be outdated/unmaintained)
-
Identify if any supported form plugins are activeIn WordPress admin, navigate to Plugins > Installed Plugins and check whether Contact Form 7, WPForms, Elementor Forms, Formidable Forms, or Ninja Forms are activeAffected if Any of these form plugins are active alongside the WP Zendesk plugin (the vulnerability affects integration with these forms)
-
Confirm plugin is accessible without authenticationCheck the WordPress site is publicly accessible and the WP Zendesk plugin endpoints are not protected by additional authentication or access controlsAffected if The WordPress site allows unauthenticated access to plugin functionality (this is the default state for this vulnerability)
You are affected if the WP Zendesk plugin version is 1.1.4 or lower and any of the supported form plugins (Contact Form 7, WPForms, Elementor, Formidable, or Ninja Forms) are active on the same WordPress site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to the latest version immediately. If no update is available, remove the plugin entirely to eliminate the attack surface.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49105 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data