springframework-social Cross-Site Request Forgery vulnerability

published 2017-08-22 9 y ago modified 2026-06-17 4 mo ago also GHSA-w5r6-gx3q-hmxj , EUVD-2022-5505

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

Cross-site request forgery (CSRF) vulnerability in springframework-social before 1.1.3.

Patch / fix

fixed in 2

maven org.springframework.social:spring-social-core 1.1.3.RELEASE
vmware spring_social 1.1.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-5258 updated 2025-11-21 cvss 5.8

springframework-social: CSRF vulnerability when authorizing an app against OAuth 2 API provider

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
maven	org.springframework.social:spring-social-core	<1.1.3.RELEASE	1.1.3.RELEASE

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

lists.fedoraproject.org /pipermail/package-announce/2016-February/177420.html
vendor-advisory, web, third-party-advisory
bugzilla.redhat.com /show_bug.cgi?id=1305443
web, issue-tracking, third-party-advisory, vdb-entry
nvd.nist.gov /vuln/detail/CVE-2015-5258
advisory
github.com /spring-projects/spring-social
package

Sources

CVE List CVE-2015-5258
GitHub Advisory GHSA-w5r6-gx3q-hmxj
NVD CVE-2015-5258

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.

Summary