AI-generated · no human review · verify critical claims against the linked source.how it works →
phpBB OAuth improper-authentication account hijack (admin) even when OAuth disabled; CVSS 9.8; fixed 3.3.17
cve
· CVE-2026-48611
Coverage
1
first 2026-06-16 → last 2026-10-21
Latest activity
2026-06-16
One unauthenticated request yields a session as any phpBB user on default boards, and only an upgrade fixes it
Peak priority
notable
1 notable
Targets
·
no sector or region stated
Sources cited
7
6 hosts
Action items (1)
Do-now tasks recorded on the entries about CVE-2026-48611, newest first. Check the date before acting on an older one.
Upgrade every internet-reachable phpBB board to 3.3.17: CVE-2026-48611 gives a session as any user on default installations from one unauthenticated request, proof-of-concept requests are public, and no configuration change closes it.
1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)
Initial AccessExploit Public-Facing Application
Initial Access TA0001
T1190Exploit Public-Facing Application×1
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.
phpBB 3.3.17, released on 2026-06-06, fixes two authentication flaws disclosed by Pentest-Tools.com (Pentest-Tools.com, 2026-06-08). CVE-2026-48611 (CVSS 9.4 per Pentest-Tools) lets a single unauthenticated POST to the user control panel's login-link handler with auth_provider=apache route the login through phpBB's Apache provider, which checks only that the HTTP Basic username matches and that the password is non-empty, never comparing the password with the stored hash, and returns a valid session as any active user on default installations (Pentest-Tools.com, 2026-06-08). The CVE record, assigned by HackerOne as numbering authority, scores it CVSS 3.0 9.8 and describes improper authentication checks in phpBB's OAuth implementation that allow account hijacking even when OAuth is not configured or enabled (ENISA EUVD, 2026-06-12); heise reports the same 9.8 (heise online, 2026-06-15). A known username is enough, and a default board's public member list supplies it (Pentest-Tools.com, 2026-06-08). Sources disagree on whether the session also reaches the Administration Control Panel. Pentest-Tools first wrote that the panel's separate password prompt stops the attacker, then added on 2026-06-15 that an attacker can in fact directly access the panel after impersonating an administrator (Pentest-Tools.com, 2026-06-08). Aikido says a password check in front of the panel cannot be bypassed, which is why it rules out direct remote code execution even through the Extension Catalog (Aikido Security, 2026-06-10). Aikido reported the flaw to phpBB on 2026-06-02 and says it affects every version up to 3.3.16 and 4.0.0-a2 (Aikido Security, 2026-06-10), and heise reports that Aikido and Pentest-Tools' researcher found it independently (heise online, 2026-06-15).
CVE-2026-48612 (CVSS 8.3 per Pentest-Tools; 8.0 under CVSS 3.0 in its CVE record (ENISA EUVD, 2026-06-12), the score heise reports (heise online, 2026-06-15)) affects only boards where an administrator has enabled OAuth login with a Google, Facebook or Bitly provider. Missing OAuth state validation and a missing CSRF check on the account-link endpoint let an attacker bind their own identity-provider account to a logged-in victim who opens a crafted link, which gives the attacker a permanent OAuth login to the victim's account (Pentest-Tools.com, 2026-06-08). Pentest-Tools added proof-of-concept requests for both flaws to its write-up on 2026-07-04 (Pentest-Tools.com, 2026-06-08). Neither CVE is in CISA's KEV catalog as of 2026-09-29 (CISA KEV catalog, 2026-09-29).
Triage: the bypass works by forcing the Apache provider instead of the configured one (Pentest-Tools.com, 2026-06-08), so on a board that uses database authentication, a login request naming the Apache provider is the exploit path, not a misconfigured client.
The main text above gave CVE-2026-48611 only the 9.8 score, said no public exploit code existed and advised disabling OAuth as a stop-gap, although the flaw is reachable even where OAuth is not configured or enabled (ENISA EUVD, 2026-06-12). Pentest-Tools.com scores it 9.4 and shows a single unauthenticated request through phpBB's Apache authentication provider that yields a valid session as any active user, administrators included, on default installations of phpBB 3.3.16 and earlier, fixed in 3.3.17 with no configuration workaround. It published proof-of-concept requests on 2026-07-04 (Pentest-Tools.com, 2026-06-08). Pentest-Tools is one of two independent discoverers, with Aikido (heise online, 2026-06-15). CVE-2026-48612 needs OAuth enabled and a victim who opens a crafted link, and it binds the attacker's OAuth identity to the victim's account rather than hijacking a session (Pentest-Tools.com, 2026-06-08). Disabling OAuth helps only against CVE-2026-48612. No cited source says phpBB is common at European universities or municipalities.
The CVSS 9.8 for CVE-2026-48611 and 8.0 for CVE-2026-48612 that heise reports are the CVE records' own CVSS 3.0 scores, assigned by HackerOne as numbering authority (ENISA EUVD, 2026-06-12; ENISA EUVD, 2026-06-12); Pentest-Tools.com, which found both flaws, scores them 9.4 and 8.3 (Pentest-Tools.com, 2026-06-08). The CVE record for CVE-2026-48611 describes improper authentication checks in phpBB's OAuth implementation that allow account hijacking even when OAuth is not configured or enabled (ENISA EUVD, 2026-06-12). That wording stands; what does not hold is disabling OAuth as a stop-gap, which leaves this flaw open.