CVE-2020-8226 json
phpBB Server-Side Request Forgery Vulnerability
published 2020-08-17 6 y ago modified 2026-06-17 4 mo ago also BIT-phpbb-2020-8226 , EUVD-2022-4376 , GHSA-jhm9-h84h-rw83
- cvss
- 5.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
A vulnerability exists in phpBB <v3.2.10 and <v3.3.1 which allowed remote image dimensions check to be used to SSRF.
Patch / fix
- packagist phpbb/phpbb 3.2.10, 3.3.1
- bitnami phpbb 3.2.10, 3.3.1
- phpbb phpbb 3.2.10, 3.3.1
Exploit prediction
0.97% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
| NVD | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| OSV | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | phpbb/phpbb | >=3.2.0, <3.2.10 >=3.3.0, <3.3.1 |
3.2.10 3.3.1 |
| bitnami | phpbb | <3.2.10 >=3.3.0, <3.3.1 |
3.2.10 3.3.1 |
Affected products
- n/a https://github.com/phpbb/phpbb
Classification
References
-
phpbb.com
/community/viewtopic.php?f=14&t=2562631
web, patch, release-notes, vendor-advisory
-
phpbb.com
/community/viewtopic.php?f=14&t=2562636
web, patch, release-notes, vendor-advisory
-
github.com
/phpbb/phpbb-app/commit/0cfaaafb386d58576d200d56f1acdbcc2f2376e8
web
-
github.com
/phpbb/phpbb-app/commit/efc0a146bf12125eeb71d00470af774326a7bf0a
web
-
nvd.nist.gov
/vuln/detail/CVE-2020-8226
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/phpbb/phpbb/CVE-2020-8226.yaml
web
-
github.com
/phpbb/phpbb-app
package
Sources
- CVE List CVE-2020-8226
- GitHub Advisory GHSA-jhm9-h84h-rw83
- NVD CVE-2020-8226
- OSV BIT-phpbb-2020-8226
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.