WordPress WP w3all phpBB plugin <= 3.1.9 - SQL Injection vulnerability
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. WP w3all phpBB plugin version 3.1.9 or earlier (<= 3.1.9) is affected
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The WP w3all phpBB plugin for WordPress, up to and including version 3.1.9, contains an SQL injection flaw that lets an attacker over the network read or change database contents and disrupt the site. Exploiting it requires an account with low privileges, and no user interaction is needed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in axew3.com WP w3all phpBB wp-w3all-phpbb-integration allows SQL Injection.This issue affects WP w3all phpBB: from n/a through 3.1.9.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
WP w3all phpBB plugin version 3.1.9 or earlier (<= 3.1.9) is affectedUpgrade to a fixed version: 3.2.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wp-w3all-phpbb-integration
through 3.1.9
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121769
Is CVE-2026-121769 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin builds database queries from input without properly sanitizing it, so crafted input can change the queries the site runs. The advisory says this could let someone read, modify, or delete the entire database, including user accounts and private data.Source: patchstack.com
Which versions are affected by CVE-2026-121769?
wp-w3all-phpbb-integration: through 3.1.9.Source: cve.now feed data
Am I affected, and how do I check?
WP w3all phpBB plugin version 3.1.9 and earlier are affected, with the vendor range starting at 0 through 3.1.9. To check, look at the plugin version shown on the WordPress Plugins screen or in the plugin's main file header.Source: patchstack.com
How do I fix CVE-2026-121769?
Update the WP w3all phpBB plugin to version 3.2.0 or later, which the advisory states resolves the vulnerability.Source: patchstack.com