NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CSRF in Play FrameworkGHSA-cf8j-64h9-6q58

MEDIUMFix: playframework/playframework#10285

GHSA-cf8j-64h9-6q58 is a medium-severity (CVSS 6.5) Cross-Site Request Forgery (CSRF) vulnerability in com.typesafe.play:play_2.12. A fix is available for com.typesafe.play:play_2.12 — see the affected versions and patch details below.

Also known asCVE-2020-12480
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk
0.00%0.34%0.68%1.03%0.0%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕com.typesafe.play:play_2.12☕com.typesafe.play:play_2.12

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

Description

In Play Framework 2.6.0 through 2.8.1, the CSRF filter can be bypassed by making CORS simple requests with content types that contain parameters that can't be parsed.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.typesafe.play:play_2.12all versions2.7.5com.typesafe.play:play_2.12:2.7.5
☕Mavencom.typesafe.play:play_2.12≥ 2.8.0&&< 2.8.22.8.2com.typesafe.play:play_2.12:2.8.2

Affected Products

1 product · 3 configurations
Application
play frameworklightbend
≥ 2.8.0 && ≤ 2.8.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.typesafe.play:play_2.12, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.typesafe.play:play_2.12 to 2.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cf8j-64h9-6q58 is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

In Play Framework 2.6.0 through 2.8.1, the CSRF filter can be bypassed by making CORS simple requests with content types that contain parameters that can't be parsed.
O3 Security · Impact-Aware SCA

Is GHSA-cf8j-64h9-6q58 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CSRF in Play Framework (Medium 6.5)