{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-18056 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18056 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18056 is a high-severity authentication bypass vulnerability in HivePress Authentication, published on 6 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-18056 and fix it if it is affected.\n\nWhat it is: CVE-2026-18056 is a high-severity authentication bypass vulnerability in HivePress Authentication, published on 6 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-18056 in the wild and no public exploit code.\n\nAffected product: HivePress Authentication. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-18056/ (Markdown: https://insights.sbomify.com/CVE-2026-18056/index.md)","id":"CVE-2026-18056","markdown":"https://insights.sbomify.com/CVE-2026-18056/index.md","name":"CVE-2026-18056","record":{"aliases":["GHSA-55w6-5hh5-wj3r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication and log in as any user, including administrators, by supplying a valid Facebook access token without proper validation.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Auth bypass in HivePress Authentication","id":"CVE-2026-18056","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Events Manager \u003c 7.4.1 - Subscriber+ Booking Consent Record Tampering via SQL Injection","id":"CVE-2026-18057"},"packages":[],"prev":{"headline":"ManageWP Worker \u003c 4.9.37 - Unauthenticated Authentication Bypass via Unsigned Auto-Login Parameters","id":"CVE-2026-18052"},"products":["HivePress Authentication"],"published":"2026-09-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-07","vendors":["hivepress"]},"summary":"Unauthenticated attackers can bypass authentication and log in as any user, including administrators, by supplying a valid Facebook access token without proper validation.","url":"https://insights.sbomify.com/CVE-2026-18056/"}