CVE-2017-1000419 json
phpBB Server-Side Request Forgery (SSRF)
published 8y ago modified 4mo ago also GHSA-9jm4-rg99-566c , EUVD-2022-3403
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
phpBB version 3.2.0 is vulnerable to SSRF in the Remote Avatar function resulting allowing an attacker to perform port scanning, requesting internal content and potentially attacking such internal services via the web application.
Patch / fix
- packagist phpbb/phpbb 3.2.1
Is CVE-2017-1000419 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.32% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- sec-consult.com https://www.sec-consult.com/en/blog/advisories/phpbb-server-side-request-forgery-vulnerability/index.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | phpbb/phpbb | >=3.2.0, <3.2.1 |
3.2.1 |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
sec-consult.com
/en/blog/advisories/phpbb-server-side-request-forgery-vulnerability/index.html
web, exploit, third-party-advisory
-
phpbb.com
/community/viewtopic.php?f=14&p=14782136
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-1000419
advisory
-
github.com
/phpbb/phpbb-app
package
Sources
- CVE List CVE-2017-1000419
- GitHub Advisory GHSA-9jm4-rg99-566c
- NVD CVE-2017-1000419
Fencer Intel 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.