CVE-2026-18056 json
HivePress Authentication <= 1.1.4 - Unauthenticated Authentication Bypass via 'access_token' Parameter to Facebook Authenticator
published 2mo ago modified 2mo ago also EUVD-2026-72043
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
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 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.
Patch / fix
Is CVE-2026-18056 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2mo ago
Exploit prediction
0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- hivepress HivePress Authentication
Classification
- Weakness
-
- CWE-287 Improper Authentication
- Technology feeds
References
- github.com /hivepress/hivepress-authentication/commit/f97d9109002905cf57597d15c535d1155dc64657
- wordfence.com /threat-intel/vulnerabilities/id/c0ba6392-e6f7-479a-8b9b-9cea4b140c71?source=cve
- developers.facebook.com /docs/facebook-login/guides/advanced/manual-flow/#confirm
- plugins.trac.wordpress.org /browser/hivepress-authentication/tags/1.1.4/includes/components/class-facebook-authentication.php#L59
- plugins.trac.wordpress.org /browser/hivepress-authentication/tags/1.1.4/includes/controllers/class-authentication.php#L84
- plugins.trac.wordpress.org /changeset/3664231/hivepress-authentication
Sources
- CVE List CVE-2026-18056
- NVD CVE-2026-18056
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.