dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-0910

HIGH · 8.8 CVSS v3.1 Published 2026-02-11
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
The wpForo Forum plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.4.13 via deserialization of untrusted input in the 'wpforo_display_array_data' function. This makes it possible for authenticated attackers, with Subscriber-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 wpForo Forum plugin for WordPress versions up to 2.4.13 are vulnerable to PHP Object Injection via deserialization of untrusted input in the 'wpforo_display_array_data' function. Authenticated attackers with Subscriber-level access can inject arbitrary PHP objects; however, actual exploitation requires a POP chain from another installed plugin or theme to achieve code execution, file deletion, or data exfiltration.

MitigationUpdate wpForo Forum plugin to version 2.4.14 or later, and audit all other installed plugins and themes for known 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
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. Confirm wpForo Forum plugin is installed
    Access WordPress admin panel under Plugins > Installed Plugins and locate wpForo Forum, or inspect the plugin directory at wp-content/plugins/
    Affected if wpForo Forum plugin is present in the WordPress installation
  2. Identify installed wpForo version
    View the plugin version in WordPress admin under Plugins > Installed Plugins, or open the main plugin file (typically plugin.php or index.php in the wpforo folder) and check the Version header in the plugin comment block
    Affected if Version is 2.4.13 or earlier (any version up to and including 2.4.13)
  3. Verify subscriber-level access exists
    Check WordPress user roles under Users > All Users to confirm if any accounts with Subscriber role exist
    Affected if At least one Subscriber-level user account is present on the site
  4. Confirm wpForo forum functionality is active
    Search WordPress content for wpForo shortcodes (commonly [wpforo] or similar) or visit the forum URL to verify the forum is accessible
    Affected if wpForo forum pages are published and accessible to authenticated users
  5. Audit other plugins for POP chain potential
    Review all installed plugins and themes for known PHP Object Injection vulnerabilities or unserialize() calls that could be chained with this flaw
    Affected if Any additional plugin or theme with exploitable deserialization is installed alongside vulnerable wpForo version

Environment is affected if wpForo Forum plugin version 2.4.13 or lower is installed and any Subscriber-level user can access wpForo functionality, especially when other plugins with exploitable unserialize() calls are also present.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update wpForo Forum plugin to version 2.4.14 or later, and audit all other installed plugins and themes for known POP chains that could be chained with this vulnerability.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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