dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-7566

MEDIUM · 6.6 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
The LearnPress – Backup & Migration Tool plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 4.1.4 via deserialization of untrusted input . This makes it possible for authenticated attackers, with administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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

The LearnPress Backup & Migration Tool plugin for WordPress is vulnerable to PHP Object Injection in versions up to 4.1.4. The vulnerability stems from unsafe deserialization of untrusted input, allowing authenticated administrators to inject arbitrary PHP objects. While no POP chain exists within the plugin itself, the vulnerability becomes exploitable if other installed plugins or themes contain a POP chain, potentially enabling file deletion, data theft, or code execution.

MitigationUpdate the LearnPress Backup & Migration Tool plugin to the latest version (4.1.5 or higher). Conduct an audit of all installed plugins and themes to identify and remediate any that contain POP chains that could be chained with this 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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/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 LearnPress - Backup & Migration Tool is installed
    Navigate to WordPress admin > Plugins > Installed Plugins, or use WP-CLI: wp plugin list --name='learnpress-backup'
    Affected if The plugin is listed in the installed plugins
  2. Check installed plugin version
    View the plugin details in WordPress admin or check the main plugin file header for 'Version:' value
    Affected if Installed version is 4.1.4 or lower (any version up to and including 4.1.4)
  3. Confirm administrator-level accounts exist
    Review user accounts in WordPress admin > Users, or check wp_users table for user_level >= 10 or wp_capabilities containing 'administrator'
    Affected if Any administrator-level user account exists in the WordPress installation
  4. Audit for plugins or themes with unserialize() calls
    Review all installed plugins and themes for known PHP Object Injection vulnerabilities or POP chain gadgets, particularly those using unserialize() on user-controlled data
    Affected if A separate vulnerable plugin or theme with a usable POP chain is installed alongside the affected LearnPress plugin

User is affected if LearnPress - Backup & Migration Tool version 4.1.4 or lower is installed, an administrator account exists, AND a plugin/theme with a POP chain is present for full exploitation impact

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 LearnPress Backup & Migration Tool plugin to the latest version (4.1.5 or higher). Conduct an audit of all installed plugins and themes to identify and remediate any that contain POP chains that could be chained with this vulnerability.

Recommended fix Moderate confidence

version 4.1.5 or later (check WordPress plugin repository for latest fixed release)

  1. 1. Check the currently installed version of the LearnPress – Backup & Migration Tool plugin in WordPress admin under Plugins > Installed Plugins
  2. 2. Navigate to Plugins > Add New > Upload Plugin or check the WordPress plugin repository for the latest version
  3. 3. Update the plugin to the latest available version (version 4.1.5 or higher if available)
  4. 4. Verify the update completed successfully by confirming the new version number
  5. 5. Test that the plugin's backup and migration functionality still works correctly after the update
  6. 6. If no fixed version is available in the WordPress repository, consider temporarily disabling the plugin until a patch is released
Caveat Minor or patch updates typically do not introduce breaking changes, but test backup/restore functionality after upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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