How severe is CVE-2019-16107?

CVE-2019-16107 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-16107?

CVE-2019-16107 affects the following packages: phpbb/phpbb (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-16107?

Update phpbb/phpbb to 3.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16107 is resolved across your whole dependency graph.

How do I detect CVE-2019-16107 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpbb/phpbb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2019-16107 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2019-16107?

O3 pinpoints whether CVE-2019-16107 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2019-16107 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-16107 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2019-16107?

CVE-2019-16107 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-16107 published, and has it been updated?

CVE-2019-16107 was published on March 11, 2020 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2019-16107

MEDIUM

CVE-2019-16107 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in phpbb/phpbb. O3 Security confirms whether CVE-2019-16107 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

phpBB Cross-Site Request Forgery (CSRF)

Also known asGHSA-wg24-9xm9-593v

Published

Mar 11, 2020

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘phpbb/phpbb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Missing form token validation in phpBB 3.2.7 allows CSRF in deleting post attachments.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpbb/phpbb`	≥ 3.2.7&&< 3.2.8	3.2.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpbb/phpbb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update phpbb/phpbb to 3.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16107 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2019-16107 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2019-16107. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Missing form token validation in phpBB 3.2.7 allows CSRF in deleting post attachments.

O3 Security · Impact-Aware SCA

Is CVE-2019-16107 in your dependencies?

O3 detects CVE-2019-16107 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works