dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-68531

HIGH · 8.8 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Deserialization of Untrusted Data vulnerability in modeltheme ModelTheme Addons for WPBakery and Elementor modeltheme-addons-for-wpbakery allows Object Injection.This issue affects ModelTheme Addons for WPBakery and Elementor: from n/a through < 1.5.6.

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 · moderate confidence

A deserialization vulnerability in the ModelTheme Addons plugin for WPBakery and Elementor allows unauthenticated attackers to inject malicious PHP objects, potentially leading to remote code execution. The vulnerability affects all versions prior to 1.5.6.

MitigationUpdate ModelTheme Addons for WPBakery and Elementor to version 1.5.6 or later to patch the deserialization vulnerability.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if ModelTheme Addons plugin is installed
    Check your WordPress plugins directory for the ModelTheme Addons plugin folder, or list installed plugins via wp-cli: wp plugin list --status=active --format=csv
    Affected if ModelTheme Addons is present in the plugins directory and active
  2. Check the installed plugin version
    Open the main plugin file (usually mt-addons.php or similar in /wp-content/plugins/mt-addons/) and look for the 'Version' header in the plugin comment block, or run: grep -i 'Version:' /path/to/plugins/mt-addons/*.php
    Affected if Version is lower than 1.5.6 or the version cannot be determined
  3. Locate unserialize() calls in the plugin code
    Search the plugin source code for unserialize() function calls: grep -rn 'unserialize' /path/to/plugins/mt-addons/
    Affected if Any unserialize() calls are found in the plugin files
  4. Verify if unserialize() processes user-supplied input
    Examine each unserialize() call found and trace whether $_GET, $_POST, $_REQUEST, or other user-controlled input reaches it directly or via variables
    Affected if User input (request parameters, POST/GET data) flows into the unserialize() function without sanitization
  5. Check if the plugin handles serialized data from external sources
    Review any AJAX handlers, form processing, or API endpoints in the plugin that accept and unserialize data from requests
    Affected if The plugin accepts and unserializes data from unauthenticated or authenticated user requests

A user is affected if the ModelTheme Addons plugin version is below 1.5.6 and the plugin contains unserialize() calls that process user-controlled input from HTTP requests.

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 ModelTheme Addons for WPBakery and Elementor to version 1.5.6 or later to patch the deserialization vulnerability.

Recommended fix Moderate confidence

1.5.6

  1. 1. Back up your WordPress site and database before performing any updates
  2. 2. Navigate to WordPress Dashboard > Plugins
  3. 3. Find 'ModelTheme Addons for WPBakery and Elementor' in the installed plugins list
  4. 4. Click 'Update now' if an update is available, or manually update to version 1.5.6
  5. 5. After updating, clear any caching mechanisms (site cache, CDN cache)
  6. 6. Verify the plugin version shows 1.5.6 or higher in the plugins list

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68531 — 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-2025-68531 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