CVE-2020-8226: phpBB Server-Side Request Forgery Vulnerability

phpbb/phpbb Updated 02 Oct 2025

Summary

24/05/2022
Yes i
Moderate
5.8

CVE-2020-8226: phpBB Server-Side Request Forgery Vulnerability. Affects phpbb/phpbb across 2 version ranges.

>= 3.2.0, < 3.2.10 >= 3.3.0, < 3.3.1

Fixed in 3.2.10 or 3.3.1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2020-8226 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

phpBB is a popular open-source forum software written in PHP. It provides a platform for online discussion and community building. The vulnerability identified as CVE-2020-8226 affects phpBB versions prior to v3.2.10 and v3.3.1. This vulnerability allows an attacker to exploit a remote image dimensions check and perform Server-Side Request Forgery (SSRF) attacks.

Vulnerability Detail

The vulnerability in phpBB arises from the remote image dimensions check feature, which can be abused to initiate SSRF attacks. By manipulating the image dimensions check, an attacker can trick the server into making requests to arbitrary URLs, potentially leading to unauthorized access to internal resources or sensitive information. This vulnerability has a CVSS score of 5.8, indicating a moderate severity level.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.2.0, < 3.2.10 3.2.10
    composer require phpbb/phpbb:3.2.10
  • >= 3.3.0, < 3.3.1 3.3.1
    composer require phpbb/phpbb:3.3.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround available for this vulnerability. It is essential to apply the recommended fix by upgrading to the patched versions of phpBB.

Conclusion

The phpBB Server-Side Request Forgery (SSRF) vulnerability (CVE-2020-8226) allows an attacker to exploit the remote image dimensions check feature and perform unauthorized requests. To mitigate this vulnerability, it is crucial to upgrade to phpBB v3.2.10 or v3.3.1. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for phpbb/phpbb →

Share this vulnerability

FAQ

phpBB is an open-source forum software written in PHP, providing a platform for online discussion and community building.

Server-Side Request Forgery (SSRF) is a vulnerability that allows an attacker to make requests from the server to arbitrary URLs, potentially accessing internal resources or sensitive information.

This vulnerability can be exploited to perform SSRF attacks, potentially leading to unauthorized access to internal resources or sensitive information.

To fix this vulnerability, upgrade to phpBB v3.2.10 or v3.3.1, depending on the installed version.

No, there is no specific workaround available. It is recommended to apply the fix by upgrading to the patched versions of phpBB.

Related vulnerabilities

Recent vulnerabilities recorded for phpbb/phpbb.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 3.2.0, < 3.2.10 3.2.10
    composer require phpbb/phpbb:3.2.10
  • >= 3.3.0, < 3.3.1 3.3.1
    composer require phpbb/phpbb:3.3.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback