/

CVE-2026-18056

Severity:

HIGH RISK

(7.5)

Authentication Bypass (CWE-287) in HivePress Plugin

CVE-2026-18056

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-287

Impact:

Account Takeover

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The HivePress Authentication plugin for WordPress does not sufficiently validate Facebook access tokens before using their identity data to authenticate users. An attacker who obtains a valid token associated with an existing WordPress user's email may be able to access that account, potentially including an administrator account.

Affected context

The vulnerability occurs in the HivePress Authentication plugin's Facebook authentication flow when the application accepts an attacker-supplied access_token and forwards it to the Facebook Graph API. It is relevant when the returned identity is trusted without verifying the token's intended application, audience, or other issuer-specific properties, and when the associated email belongs to an existing WordPress user.

Exploit preconditions

  • Attack surface: The WordPress authentication endpoint supporting

Facebook login

  • Required access: No WordPress account is required, but the attacker

must obtain a valid Facebook access token associated with an identity

matching a target user's email

  • Trigger point: Processing of the access_token by the Facebook

authenticator

  • Why exploitation is possible: The authentication flow trusts identity

information returned for the token without performing application ID or

audience validation

Why this happens

The underlying issue is insufficient validation of a third-party authentication assertion. The application consumes identity data returned by the Facebook Graph API without independently confirming that the token was issued for the configured application, such as through token debugging and app_id comparison. This maps to CWE-287: Improper Authentication, because the application accepts an identity claim without establishing that the credential is valid for the intended relying application.

Potential impact

  • An attacker may authenticate as an existing WordPress user.
  • An attacker could take over an administrator account.
  • Unauthorized users may gain access to protected site content and functions.
  • Site data, settings, or content could be modified.
  • A compromised administrator account may be used for further site compromise.

General mitigation guidance

Mitigation generally focuses on treating third-party tokens as untrusted assertions until they are fully verified. Secure-by-default authentication flows should validate token signatures or provider responses, confirm issuer, audience, application identity, expiry, and required scopes, and bind the resulting identity to a verified provider account. Applications should avoid using an email claim alone as proof of account ownership, reduce trust in client-supplied identity parameters, apply least privilege to authenticated roles, and require additional safeguards for administrative access.

How teams detect issues like this

Detection can include static analysis and code review checks for authentication handlers that trust provider-returned email or ID values without audience validation. Reviewers can look for missing token-debugging calls, absent application ID comparisons, direct use of client-supplied access_token values, and account lookup based solely on email. Runtime monitoring can flag unusual social-login activity, administrative logins through newly observed provider identities, and authentication events where provider and configured application identifiers do not match. Automated security review tools may help enforce these patterns in CI.

Sources

SourceLink
developers.facebook.comdevelopers.facebook.com/docs/facebook-login/guides/advanced/manual-flow/#confirm
github.comgithub.com/hivepress/hivepress-authentication/commit/f97d9109002905cf57597d15c535d1155dc64657
plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/hivepress-authentication/tags/1.1.4/includes/components/class-facebook-authentication.php#L59
plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/hivepress-authentication/tags/1.1.4/includes/controllers/class-authentication.php#L84
plugins.trac.wordpress.orgplugins.trac.wordpress.org/changeset/3664231/hivepress-authentication
wordfence.comwordfence.com/threat-intel/vulnerabilities/id/c0ba6392-e6f7-479a-8b9b-9cea4b140c71?source=cve

Frequently asked

questions

It can be triggered through the WordPress authentication surface without

prior WordPress authentication, but exploitation still requires the attacker

to obtain a valid Facebook access token associated with a target identity.

No. The vulnerable login flow may authenticate the attacker as an existing

WordPress user when the token's returned identity matches that user's email.

Validate the token with the identity provider and confirm its issuer,

audience, application ID, validity period, and relevant claims before using

it for account authentication. Do not treat an email claim alone as proof

of authorization.

Use provider-supported verification mechanisms, minimize trust in

client-supplied tokens and identity fields, apply least privilege to linked

accounts, and test social-login flows for token substitution and audience

validation failures.

Find out what's already
exploitable in your codebase.