dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-49107

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
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 Thrive Apprentice < 10.8.10.2 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

This is an unauthenticated PHP Object Injection vulnerability in the Thrive Apprentice WordPress plugin. Attackers can inject malicious PHP objects without authentication, potentially leading to remote code execution through magic methods like __wakeup, __destruct, or __invoke when the application deserializes untrusted input.

MitigationUpgrade Thrive Apprentice to version 10.8.10.2 or later. If immediate patching is not possible, consider disabling the plugin or implementing a WAF rule to block deserialization-related attack patterns.

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. Confirm Thrive Apprentice plugin is installed
    Check for the plugin directory at wp-content/plugins/thrive-apprentice/ or use wp plugin list in WP-CLI, or inspect the plugins page in WordPress admin
    Affected if The plugin directory or listing shows Thrive Apprentice is present in the WordPress installation
  2. Identify installed plugin version
    Read the main plugin file (usually thrive-apprentice/thrive-apprentice.php) and locate the 'Version:' header in the plugin comment block, or query the wp_options table for the option_name containing 'thrive_apprentice_version'
    Affected if The version number found is lower than 10.8.10.2 (for example, 10.8.10.1, 10.8.9.0, or earlier)
  3. Verify the plugin is active
    Check WordPress admin plugins page status, or query wp_cli to check if the plugin is network-active in multisite, or inspect the wp_options table where option_name = 'active_plugins'
    Affected if The plugin shows as active or network-active, meaning the vulnerable code is loaded and can process requests
  4. Confirm no WAF or deserialization filtering is applied
    Inspect any web application firewall configurations or server-level request filtering that may be blocking PHP deserialization patterns in incoming requests (check .htaccess, nginx config, or WAF plugin settings)
    Affected if No protective rules are in place to block malicious unserialize() calls or serialized object injection patterns in HTTP requests

A user is affected if Thrive Apprentice is installed with a version lower than 10.8.10.2 and the plugin is active, allowing unauthenticated attackers to inject PHP objects via deserialization vulnerabilities.

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

Upgrade Thrive Apprentice to version 10.8.10.2 or later. If immediate patching is not possible, consider disabling the plugin or implementing a WAF rule to block deserialization-related attack patterns.

Recommended fix High confidence

Thrive Apprentice version 10.8.10.2

  1. Backup your WordPress site (database and files) before performing any updates
  2. Update Thrive Apprentice plugin to version 10.8.10.2 or later via WordPress plugin dashboard, or upload the updated plugin files manually
  3. Verify the plugin version has been updated successfully in Plugins > Installed Plugins
  4. Clear any site caches if a caching plugin is in use
  5. Test critical functionality of the course/learning management system to ensure the update did not break expected behavior
Caveat Review Thrive Architect/theme compatibility notes for this release; test in staging if complex customizations exist

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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