Skip to content
Fencer Intel
high 7.5

CVE-2013-1635 json

ext/soap/soap.c in PHP before 5.3.22 and 5.4.x before 5.4.13 does not validate the relationship between the soap.wsdl_cache_dir directive a…

published 13y ago modified 4mo ago also EUVD-2013-1666

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

Summary

ext/soap/soap.c in PHP before 5.3.22 and 5.4.x before 5.4.13 does not validate the relationship between the soap.wsdl_cache_dir directive and the open_basedir directive, which allows remote attackers to bypass intended access restrictions by triggering the creation of cached SOAP WSDL files in an arbitrary directory.

Patch / fix

  • php7 openSUSE Tumbleweed 7.0.14-1.4
  • php5 openSUSE Tumbleweed 5.6.28-1.1
  • php8 openSUSE Tumbleweed 8.0.11-1.1

opensuse advisories openSUSE-SU-2024:10290-1openSUSE-SU-2024:10344-1openSUSE-SU-2024:11169-1

Is CVE-2013-1635 in your stack? 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-1635 updated cvss 5.0

php53: Arbitrary locations file write due absent validation of soap.wsdl_cache_dir configuration directive value

  • Red Hat Enterprise Linux 5 php, php53 Red Hat Enterprise Linux 6 php, php-gd, php-cli, php-dba, php-fpm, php-pdo, +20 more
    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

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

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
Technology feeds

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.