SEO Booster <= 7.4.7 - Authenticated (Subscriber+) Missing Authorization to Arbitrary Options Modification via handle_oauth_callback()
Strategic Overview
- Status
- Patched in 7.4.8
- Affected Plugin
- SEO Booster
- Affected Version
<= 7.4.7- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-15660
At a glance
CVE-2026-15660 is a medium-severity Missing Authorization vulnerability in the SEO Booster WordPress plugin, affecting versions <= 7.4.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 7.4.8; sites on affected versions should update now. Disclosed September 2026, reported by Wordfence PRISM.
Vulnerability Overview
The SEO Booster plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 7.4.7. This is due to a missing capability check on the handle_oauth_callback() function which is hooked to admin_init and processes $_GET['access_token'] and $_GET['google_email'] without verifying the caller's role. This makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the seobooster_access_token, seobooster_google_email, and seobooster_gsc_sites options and delete the seobooster_needs_reauth flag by visiting a crafted /wp-admin/ URL, disrupting the Google Search Console integration and injecting attacker-chosen data into site options via the attacker-supplied token that drives an outbound Google API request whose response is stored.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
SEO Booster <= 7.4.7 carries this weakness at access_token, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For SEO Booster the fix is 7.4.8: builds <= 7.4.7 are affected, anything from 7.4.8 onward is not.
Remediation
Update to version 7.4.8, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: SEO Booster 7.4.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in SEO Booster
- 7.2CVE-2021-24747: SEO Booster <= 3.7 Admin+ SQL Injection
CVE-2021-24747 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 4.9CVE-2026-15458: SEO Booster <= 7.3.1 SQL Injection
CVE-2026-15458 - 4.9CVE-2026-15445: SEO Booster <= 7.3.1 SQL Injection
CVE-2026-15445 - 4.3CVE-2024-32438: SEO Booster <= 3.8.9 Cross-Site Request Forgery
CVE-2024-32438
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C