Plugins · hivepress-authentication · data as of 2026-11-04
Is HivePress Authentication safe? Known vulnerabilities and latest version
- Latest version
- 1.1.5
- Last updated
- 2026-08-24
- Active installs
- 1,000+
- Known issues on record
- 1
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Allow users to sign in via third-party services. — by HivePress
What to do
- Update to the latest version (1.1.5). Anything older than 1.1.5 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get hivepress-authentication --field=version shows what you run; wp plugin update hivepress-authentication updates it.
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 7.5 CVE-2026-18056 · published 2026-09-06
Authentication bypass in HivePress Authentication (1.1.4 and older)
- Affected
- 1.1.4 and older
- Fixed in
- 1.1.5 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-18056Wordfence advisoryCode change (fix)developers.facebook.comgithub.comPlugin source
Recent activity
- 2026-08-24 — latest release on wordpress.org (1.1.5).
- 2026-09-06 — Authentication bypass disclosed (CVE-2026-18056), fixed in 1.1.5.
Get an email when HivePress Authentication has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for HivePress Authentication (hivepress-authentication) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by HivePress (3 tracked)
Types found in this plugin: Authentication bypass (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/hivepress-authentication (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/hivepress-authentication"><img src="https://laskyr.com/plugins/hivepress-authentication/badge.svg" alt="HivePress Authentication vulnerability status"></a>