Skip to content
Fencer Intel
high 7.5

CVE-2018-1259 json

Spring Data Commons, used in combination with XMLBeam, contains a property binder vulnerability caused by improper restriction of XML external entity references

published 8y ago modified 4mo ago also GHSA-m929-7fr6-cvjg , EUVD-2018-0636

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.8%
EPSS 4.8% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

Spring Data Commons, versions 1.13 prior to 1.13.12 and 2.0 prior to 2.0.7, used in combination with XMLBeam 1.4.14 or earlier versions, contains a property binder vulnerability caused by improper restriction of XML external entity references as underlying library XMLBeam does not restrict external reference expansion. An unauthenticated remote malicious user can supply specially crafted request parameters against Spring Data's projection-based request payload binding to access arbitrary files on the system.

Patch / fix

  • maven org.springframework.data:spring-data-commons 1.13.12, 2.0.7

Is CVE-2018-1259 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 Fencer

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-2018-1259 updated cvss 7.3

spring-data-commons: XXE with Spring Data’s XMLBeam integration

  • Red Hat Fuse 7.2
    fixed: vendor fix RHSA-2018:3768
  • Red Hat Text-Only RHOAR
    fixed: vendor fix RHSA-2018:1809
  • Red Hat JBoss Fuse 6 spring-data-commons Red Hat JBoss Fuse Integration Service 2 spring-data-commons Red Hat Mobile Application Platform 4 spring-data-commons
    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

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

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
maven org.springframework.data:spring-data-commons
>=1.13.0, <1.13.12
>=2.0.0, <2.0.7
1.13.12
2.0.7

Affected products

  • Pivotal Spring Data Commons

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

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.