Skip to content
Fencer Intel
high 7.5

CVE-2015-7503 json

Zend Framework Information Disclosure

published 9y ago modified 4mo ago also GHSA-pm9m-w23q-5967 , EUVD-2022-4795

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

Summary

Zend Framework before 2.4.9, zend-framework/zend-crypt 2.4.x before 2.4.9, and 2.5.x before 2.5.2 allows remote attackers to recover the RSA private key.

Patch / fix

  • packagist zendframework/zendframework 2.4.9, 2.5.2
  • packagist zendframework/zend-crypt 2.4.9, 2.5.2

Is CVE-2015-7503 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-2015-7503 updated cvss 7.1

php-ZendFramework2: Usage of vulnerable PKCS#1 v1.5 padding allows to recover RSA private key

  • 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.36% chance of exploitation in the next 30 days, higher than 71% 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
packagist zendframework/zendframework
>=2.5.0, <2.5.2
>=2.0.0, <2.4.9
2.5.2
2.4.9
packagist zendframework/zend-crypt
>=2.0.0, <2.4.9
>=2.5.0, <2.5.2
2.4.9
2.5.2

Classification

Weakness
  • CWE-320 Key Management Errors
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.