phpBB Cross-Site Request Forgery (CSRF)

published 2019-09-27 7 y ago modified 2026-06-17 4 mo ago also GHSA-6mh2-98gr-wv76 , EUVD-2022-2825

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits: 0; none known

phpBB version 3.2.7 allows the stealing of an Administration Control Panel session id by leveraging CSRF in the Remote Avatar feature. The CSRF Token Hijacking leads to stored XSS

Patch / fix

fixed in 1 distros 1

packagist phpbb/phpbb 3.2.8

phpbb3 Ubuntu Pro 14.04 LTS 3.0.12-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2019-13376

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

blog.phpbb.com https://blog.phpbb.com/category/security/ referenced PoC, tagged "exploit" by a source, unverified
ssd-disclosure.com https://ssd-disclosure.com/archives/4007/ssd-advisory-phpbb-csrf-token-hijacking-leading-to-stored-xss referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	phpbb/phpbb	<3.2.8	3.2.8

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation
CWE-352 Cross-Site Request Forgery

References

blog.phpbb.com /category/security/
exploit, vendor-advisory
ssd-disclosure.com /archives/4007/ssd-advisory-phpbb-csrf-token-hijacking-leading-to-stored-xss
web, exploit, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2019-13376
advisory
blog.phpbb.com /category/security
web
github.com /phpbb/phpbb-app
package

Sources

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.

Summary