CVE-2026-12597 - The LoginPress Pro plugin for WordPress is vulnerable to Authentication Bypass via the GitHub OAuth callback i

CVE-2026-12597 + The LoginPress Pro plugin for WordPress is vulnerable to Authentication Bypass via the GitHub OAuth callback i + High + 2026-07-09

One-sentence business risk

Broken authentication or authorization can expose tenant data and administrator actions, which buyers treat as a release blocker.

Research notes

  • Root cause: The LoginPress Pro plugin for WordPress is vulnerable to Authentication Bypass via the GitHub OAuth callback in versions up to, and including, 6.2.3.
  • Affected versions: LoginPress LoginPress Pro: 0 to < 6.2.3.
  • Fixed / safe versions: Vendor-fixed release or mitigation named by the upstream advisory.
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Exact vulnerable code pattern

if external_response.accepted: login(user)

Fixed / mitigated code pattern

verify response signature, nonce binding, audience, issuer, and session ownership before login

Dependency or runtime update:

composer show invoice-generator || true
composer require invoice-generator --with-all-dependencies
composer audit

Step-by-step integration guide

  1. Inventory invoice-generator across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to Vendor-fixed release or mitigation named by the upstream advisory or apply the exact vendor patch referenced below.
  3. Replace the vulnerable auth-bypass pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-12597-the-loginpress-pro-plugin-for-wordpress-is-vulne
source: "MITRE CVE List V5"
dependency_or_product: "invoice-generator"
affected: "LoginPress LoginPress Pro: 0 to < 6.2.3"
fixed: "Vendor-fixed release or mitigation named by the upstream advisory"
signals:
  - "auth-bypass"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-12597 (The LoginPress Pro plugin for WordPress is vulnerable to Authentication Bypass via the GitHub OAuth callback i) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to Vendor-fixed release or mitigation named by the upstream advisory. Replace the vulnerable auth-bypass pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-12597, auth-bypass, invoice-generator, MITRE CVE List V5.
  • Affected tech stack: php/composer.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, high_priority_sla.

References