CVE-2026-0910
Awaiting Analysis Awaiting Analysis - Queue
PHP Object Injection in wpForo Plugin Enables Potential Code Execution

Publication date: 2026-02-11

Last updated on: 2026-02-11

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-11
Last Modified
2026-02-11
Generated
2026-05-07
AI Q&A
2026-02-11
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wpforo wpforo to 2.4.13 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The wpForo Forum plugin for WordPress up to version 2.4.13 is vulnerable to PHP Object Injection via the deserialization of untrusted input in the 'wpforo_display_array_data' function.

This vulnerability allows authenticated attackers with Subscriber-level access or higher to inject PHP objects during the unserialization process.

However, no known POP (Property Oriented Programming) chain exists within the vulnerable plugin itself, so exploitation requires another plugin or theme installed on the site that contains such a POP chain.

If such a POP chain is present, attackers may be able to delete arbitrary files, retrieve sensitive data, or execute arbitrary code depending on the chain.


How can this vulnerability impact me? :

If exploited, this vulnerability can lead to severe impacts including deletion of arbitrary files, unauthorized retrieval of sensitive data, and execution of arbitrary code on the affected WordPress site.

The impact depends on the presence of a POP chain in other installed plugins or themes, which can be leveraged by an attacker with at least Subscriber-level access.

The vulnerability has a high CVSS v3.1 base score of 8.8, indicating high severity with potential for confidentiality, integrity, and availability impacts.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

The wpForo plugin includes an administrative debug tool accessible only to administrators that can help detect issues related to the plugin. This debug interface provides views such as User Data, Server Information, and Errors & Issues, which can help identify misconfigurations or suspicious activity.

Specifically, the debug tool can display detailed user data and meta data, server environment details (including PHP and MySQL versions), and error logs from common locations. It also performs checks for missing default user groups or inappropriate permissions that might indicate tampering.

While no direct network commands are provided, administrators can use this debug interface within the WordPress admin panel to inspect the plugin state and detect anomalies.

For command-line detection, since the vulnerability involves unsafe unserialization of PHP objects, monitoring for suspicious serialized payloads in HTTP requests or logs might help, but no specific commands are provided in the resources.


What immediate steps should I take to mitigate this vulnerability?

[{'type': 'paragraph', 'content': 'The primary mitigation is to update the wpForo plugin to version 2.4.14 or later, where the vulnerability is addressed by safely unserializing data with the option to disallow PHP object instantiation.'}, {'type': 'paragraph', 'content': 'Until the update is applied, restrict access to the plugin to trusted users only, as the vulnerability requires authenticated users with Subscriber-level access or higher.'}, {'type': 'paragraph', 'content': 'Additionally, review installed plugins and themes for any that might provide a POP chain, as the vulnerability only has impact if such chains exist.'}, {'type': 'paragraph', 'content': "Use the plugin's administrative debug tool to check for unusual user permissions or missing default user groups that could indicate exploitation."}] [1, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart