dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-49109

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Unauthenticated PHP Object Injection in Integration for Salesforce and Contact Form 7, WPForms, Elementor, Formidable, Ninja Forms <= 1.4.3 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 confidence

Unauthenticated PHP Object Injection in the Integration for Salesforce plugin affecting versions <= 1.4.3. Attackers can inject malicious PHP objects without authentication through form integrations (Contact Form 7, WPForms, Elementor, Formidable, Ninja Forms), potentially achieving remote code execution depending on available PHP classes and magic methods.

MitigationUpdate the plugin to a version newer than 1.4.3. If no patched version is available, disable the plugin immediately and consider alternative form-to-Salesforce solutions.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation and version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Integration for Salesforce' or 'Salesforce' plugin, and record the installed version number
    Affected if The plugin is installed and the version displayed is 1.4.3 or lower
  2. Check for active form integrations
    Navigate to the plugin settings page in WordPress admin, review which form integrations (Contact Form 7, WPForms, Elementor, Formidable, or Ninja Forms) are enabled or connected
    Affected if Any of the listed form integrations are active or configured in the plugin settings
  3. Verify public form submissions are accepted
    Inspect the WordPress site's form pages that use the integrated plugins (CF7, WPForms, etc.) and confirm they accept submissions without requiring authentication
    Affected if The forms allow unauthenticated submissions and are publicly accessible
  4. Confirm plugin is exposed to the web
    Check if the WordPress site is live and accessible via HTTP/HTTPS, and verify the plugin endpoint handling form submissions is reachable without authentication
    Affected if The site is publicly accessible and the plugin handles form submission requests without requiring login

You are affected if the Integration for Salesforce plugin version is 1.4.3 or lower AND any of the form integrations (Contact Form 7, WPForms, Elementor, Formidable, or Ninja Forms) are enabled and accepting unauthenticated submissions on a publicly accessible site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version newer than 1.4.3. If no patched version is available, disable the plugin immediately and consider alternative form-to-Salesforce solutions.

Recommended fix Moderate confidence

Latest version of the Salesforce integration plugin for Contact Form 7/WPForms/Elementor/Formidable/Ninja Forms (version higher than 1.4.3)

  1. Check the current version of the 'Integration for Salesforce' plugin (or the specific Salesforce integration addon for your form plugin) in WordPress admin under Plugins > Installed Plugins
  2. If the installed version is 1.4.3 or below, navigate to Dashboard > Updates or go to Plugins > Add New > Upload to upgrade to the latest version
  3. Alternatively, navigate to Plugins > Add New and search for 'Salesforce' or your specific form plugin's Salesforce integration to install the latest version
  4. After upgrading, verify the new version number in Plugins > Installed Plugins to confirm the update was applied
  5. Review the plugin's changelog on WordPress.org or the developer's website to confirm the security fix for the PHP Object Injection vulnerability is included
Caveat Review plugin changelog; minor plugin updates typically have no breaking changes, but test the integration with your forms in a staging environment if possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49109 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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