Skip to main content

phpBB CVE-2026-48612

| EUVDEUVD-2026-36380 HIGH
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-06-12 hackerone GHSA-575v-33q9-fpgm
8.0
CVSS 3.0 · Vendor: hackerone
Share

Severity by source

Vendor (hackerone) PRIMARY
8.0 HIGH
AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
vuln.today AI
8.0 HIGH

Attacker needs no phpBB credentials (PR:N) but must win an OAuth state race (AC:H) and trick a logged-in victim into clicking (UI:R); takeover yields full C/I but no direct availability loss.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (hackerone).

CVSS VectorVendor: hackerone

CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

1
Analysis Generated
Jun 12, 2026 - 03:46 vuln.today

DescriptionCVE.org

Improper state verification in the OAuth implementation could allow an attacker to manipulate the authentication flow and cause a victim’s account to be linked to an attacker-controlled account. This can result in unauthorized account linking and potential account takeover.

AnalysisAI

Account takeover in phpBB via OAuth state-verification flaw enables remote attackers to link a victim's forum account to an attacker-controlled identity provider account. Successful exploitation requires the victim to click an attacker-crafted link while authenticated, after which the attacker can authenticate as the victim through the linked external provider. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Recon
Attacker initiates OAuth flow with own IdP account
Delivery
Craft malicious callback link with attacker's authorization code
Exploit
Deliver link to logged-in victim (phish, forum PM)
Install
Victim's browser hits phpBB OAuth callback
C2
State verification bypassed, accounts linked
Execute
Attacker logs into phpBB via social provider
Impact
Full takeover of victim's forum identity

Vulnerability AssessmentAI

Exploitation Exploitation requires that the phpBB instance has an OAuth authentication provider enabled and configured (Google, Facebook, or similar social login), and that the victim is logged into the forum and clicks an attacker-supplied link while that session is active - both reflected in the CVSS metrics PR:L (victim must be authenticated) and UI:R (click required). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.0 score of 8.0 (AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H) reflects a high-impact, scope-changed CSRF requiring some preconditions: low privileges (a logged-in victim session), user interaction (clicking a link), and high attack complexity (winning the OAuth flow race or coercing the right click). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker initiates an OAuth authorization request at an identity provider using their own account, captures the resulting authorization code or pre-seeded state, and lures a logged-in phpBB user (typically an administrator) into clicking a crafted callback URL on the target forum. The phpBB OAuth handler accepts the response without correctly verifying that the state parameter belongs to the victim's session and links the attacker's external identity to the victim's forum account, after which the attacker logs in via the social provider and assumes the victim's identity.
Remediation Patch availability is indicated by the vendor advisory at https://www.phpbb.com/community/viewtopic.php?t=2672170, but the exact fixed version is not present in the supplied data - administrators should consult that thread and upgrade to the patched release noted there (Patch available per vendor advisory). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

24 hours: Confirm phpBB deployment across the organization and verify whether OAuth authentication is actively configured and in use. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-48612 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy