Skip to content
Fencer Intel
high 8.1

CVE-2013-4751 json

Symfony collectionCascaded and collectionCascadedDeeply fields security bypass

published 7y ago modified 4mo ago also GHSA-q8j7-fjh7-25v5 , EUVD-2022-4922

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

php-symfony2-Validator has loss of information during serialization

Patch / fix

  • packagist symfony/validator 2.0.24, 2.1.12, 2.2.5, 2.3.3
  • packagist symfony/symfony 2.0.24, 2.1.12, 2.2.5, 2.3.3
  • sensiolabs symfony 2.0.24, 2.1.12, 2.2.5, 2.3.3

Is CVE-2013-4751 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-2013-4751 updated cvss 4.3

php-symfony2-Validation: validation metadata serialization and loss of information

  • 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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist symfony/validator
>=2.0.0, <2.0.24
>=2.1.0, <2.1.12
>=2.2.0, <2.2.5
>=2.3.0, <2.3.3
2.0.24
2.1.12
2.2.5
2.3.3
packagist symfony/symfony
>=2.0.0, <2.0.24
>=2.1.0, <2.1.12
>=2.2.0, <2.2.5
>=2.3.0, <2.3.3
2.0.24
2.1.12
2.2.5
2.3.3

Classification

Weakness
  • CWE-20 Improper Input Validation

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.