CVE-2026-7637 CRITICAL

CVE-2026-7637: Boost <= 2.0.3 - Unauthenticated PHP Object Injection via STYXKEY-BOOST_USER_LOCATION Cookie

Vendor Pixelyoursite
Product Boost
Weakness CWE-502 · Unsafe deserialization
Published May 20, 2026
Last update May 20, 2026

CVSS base score

9.8/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

The Boost plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 2.0.3 via deserialization of untrusted input in the STYXKEY-BOOST_USER_LOCATION cookie. This makes it possible for unauthenticated attackers 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.

Explanation of Vulnerability in Simple Terms

02Summary

PixelYourSite Boost versions 2.0.3 and earlier contain a deserialization vulnerability that allows unauthenticated attackers to run arbitrary code on the site. The vulnerability exists because the product deserializes untrusted data without proper validation. An attacker can exploit this remotely over the network without requiring user interaction or authentication.

What an attacker can do

03Attacker Capabilities

Run arbitrary code on the site and take full control of it.

Potential impact on your site

04Site Impact

Complete compromise of the site, including data theft, malware injection, and site defacement.

Conditions required to exploit

05Prerequisites

Network access to the site; no authentication or user interaction required.

Key dates

06Disclosure timeline

May 20, 2026 CVE published
May 20, 2026 Record updated

Related vulnerabilities

08Related CVE