---
id: CVE-2026-18056
title: >-
  The HivePress Authentication plugin for WordPress is vulnerable to
  Authentication Bypass via the access_token parameter in all versions up to,
  and including, 1.1.4
summary: >-
  The HivePress Authentication plugin for WordPress is vulnerable to
  Authentication Bypass via the access_token parameter in all versions up to,
  and including, 1.1.4. This is due to the authenticate_user function's Facebook
  authenticator r…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'
cwe:
  - CWE-287
published: '2026-09-06'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T13:12:58.310'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-18056'
references:
  - url: >-
      https://developers.facebook.com/docs/facebook-login/guides/advanced/manual-flow/#confirm
    label: security@wordfence.com
  - url: >-
      https://github.com/hivepress/hivepress-authentication/commit/f97d9109002905cf57597d15c535d1155dc64657
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/hivepress-authentication/tags/1.1.4/includes/components/class-facebook-authentication.php#L59
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/browser/hivepress-authentication/tags/1.1.4/includes/controllers/class-authentication.php#L84
    label: security@wordfence.com
  - url: >-
      https://plugins.trac.wordpress.org/changeset/3664231/hivepress-authentication
    label: security@wordfence.com
  - url: >-
      https://www.wordfence.com/threat-intel/vulnerabilities/id/c0ba6392-e6f7-479a-8b9b-9cea4b140c71?source=cve
    label: security@wordfence.com
tags:
  - nvd
epss: 0.00342
epssPercentile: 0.24971
ingestedAt: '2026-09-06T15:57:04.891Z'
---

## Overview

The HivePress Authentication plugin for WordPress is vulnerable to Authentication Bypass via the access_token parameter in all versions up to, and including, 1.1.4. This is due to the authenticate_user function's Facebook authenticator resolving third-party identity by forwarding the attacker-supplied access_token to the Facebook Graph API and trusting the returned email and ID verbatim, without performing any application ID or audience validation — specifically, no /debug_token verification and no comparison of the token's app_id against the configured hp_facebook_app_id. This makes it possible for unauthenticated attackers to authenticate as any existing WordPress user, including administrators, whose email address is associated with a Facebook account for which the attacker can obtain any valid access token. Important Note: To exploit the vulnerability, the attacker must obtain the victim's access token.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.