Summary
CVE-2026-78362 is a critical authentication bypass vulnerability in the SEO Flow by LupsOnline WordPress plugin. The plugin fails to correctly validate the credential supplied with its API requests, allowing an unauthenticated attacker to be served as the administrator who previously configured the plugin — resulting in complete takeover of the affected WordPress site. The issue carries a CVSS v3.1 base score of 9.8 (Critical) and requires no authentication or user interaction to exploit.
Technical details
- Root cause: Improper Privilege Management (CWE-269) — the plugin’s API request handler does not properly validate the credential/API key presented by the caller, allowing that caller to be treated as the administrator account that configured the plugin.
- Trigger conditions: The plugin must have been configured on the target site (i.e., an administrator has set it up), which is described as its normal operating state — exploitation does not require any special or unusual configuration.
- Attack vector: Network — an unauthenticated remote attacker sends crafted API requests directly to the vulnerable WordPress site; no prior access, credentials, or user interaction are needed.
- Impact: Successful exploitation lets the attacker impersonate the site administrator, granting full control over the WordPress installation — including the ability to modify site configuration, content, and potentially escalate to arbitrary code execution or further compromise of the hosting environment.
Affected software
- SEO Flow by LupsOnline WordPress plugin, versions 3.0.0 through 3.0.2
- Fixed in version 3.0.3 and later
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Update the SEO Flow by LupsOnline plugin to version 3.0.3 or later, which corrects the credential validation logic for API requests.
- If immediate patching is not possible:
- Disable or deactivate the SEO Flow by LupsOnline plugin until the update can be applied.
- Restrict or firewall access to the plugin’s API endpoints at the network/WAF layer to trusted sources only.
- Review site administrator accounts and audit logs for signs of unauthorized configuration changes or unexpected content/user modifications, since exploitation grants full administrative impersonation.
- Rotate any API keys or credentials associated with the plugin’s integration after patching, in case they were exposed prior to remediation.

