CVE-2026-10035: Turnkey bbPress by WeaverTheme <= 1.7.1 - Authenticated (Administrator+) PHP Object Injection
The Turnkey bbPress by WeaverTheme plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.7.1 via deserialization of untrusted input in the wvrbbpsettoserializedvalues() function (reached through the wvrbbpsaverestore() settings-restore handler). The function reads the raw contents of an administrator-uploaded file and passes them directly to unserialize() without any validation. 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 plugin itself; however, if a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Turnkey bbPress by WeaverTheme plugin for WordPressto a version that resolves this vulnerability.Fixed in 1.7.1 - Compensating control
Ensure only trusted administrators (administrator-level access and above) can access and use the vulnerable plugin features, since exploitation requires authenticated attackers with administrator-level access and above to trigger the PHP Object Injection.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-10035?
CVE-2026-10035 has a severity rating of medium with a score of 6.6.
How do I fix CVE-2026-10035?
To fix CVE-2026-10035, update the Turnkey bbPress by WeaverTheme plugin to version 1.7.2 or later.
What type of vulnerability is CVE-2026-10035?
CVE-2026-10035 is an authenticated PHP Object Injection vulnerability.
Who is affected by CVE-2026-10035?
Users of the Turnkey bbPress by WeaverTheme plugin for WordPress, specifically those using versions 1.7.1 and prior, are affected.
What is the exploit method for CVE-2026-10035?
CVE-2026-10035 can be exploited through the deserialization of untrusted input in the settings-restore handler.