EUVD-2026-63313
GHSA-rxwj-6jrc-7pm8
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Network-reachable via HTTP, low complexity; subscriber auth required (PR:L); scope changes to shared DB; no integrity impact confirmed by description.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Lifecycle Timeline
2DescriptionCVE.org
Subscriber SQL Injection in WP w3all phpBB <= 3.0.5 versions.
AnalysisAI
SQL injection in the WP w3all phpBB WordPress plugin (versions ≤ 3.0.5) allows any authenticated subscriber to extract sensitive data from the underlying database via unsanitized query input. The CVSS scope change metric (S:C) combined with high confidentiality impact (C:H) indicates the injection can reach beyond the plugin's own data - potentially exposing phpBB user credentials, private messages, or WordPress core tables. …
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
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the attacker to hold a valid WordPress subscriber-level account on the target site, which is the lowest default user role in WordPress. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 base score of 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L) reflects a network-reachable, low-complexity flaw requiring only subscriber-level access - meaning any registered user on the WordPress site can attempt exploitation without further privilege escalation. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker registers a free subscriber account on the target WordPress site and then sends a crafted HTTP request to a vulnerable plugin endpoint, injecting SQL syntax into a user-controlled parameter. The injected query is executed against the shared database, returning rows from the WordPress or phpBB user tables - including email addresses and password hashes - in the HTTP response or via time-based blind inference. … |
| Remediation | The primary fix is to upgrade WP w3all phpBB to a version beyond 3.0.5 once the vendor releases a patched build; consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wp-w3all-phpbb-integration/vulnerability/wordpress-wp-w3all-phpbb-plugin-3-0-5-sql-injection-vulnerability for confirmed fix version details. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: disable the WP w3all phpBB plugin on all WordPress installations running version 3.0.5 or earlier, or immediately restrict database access to prevent subscriber-level accounts from executing arbitrary queries. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Wp W3All Phpbb
View allSame weakness CWE-89 – SQL Injection
View allShare
External POC / Exploit Code
Leaving vuln.today