CVE-2013-1824 json
The SOAP parser in PHP before 5.3.22 and 5.4.x before 5.4.12 allows remote attackers to read arbitrary files via a SOAP WSDL file containin…
published 13y ago modified 4mo ago also EUVD-2013-1842
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.3%
- EPSS 4.3% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
The SOAP parser in PHP before 5.3.22 and 5.4.x before 5.4.12 allows remote attackers to read arbitrary files via a SOAP WSDL file containing an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue in the soap_xmlParseFile and soap_xmlParseMemory functions.
Patch / fix
- php php 5.3.22, 5.4.12
- apple mac_os_x 10.8.5
- php7 openSUSE Tumbleweed 7.0.14-1.4
- php5 openSUSE Tumbleweed 5.6.28-1.1
opensuse advisories openSUSE-SU-2024:10290-1openSUSE-SU-2024:10344-1
Is CVE-2013-1824 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 FencerExploit prediction
4.31% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
- Technology feeds
References
-
bugzilla.redhat.com
/show_bug.cgi?id=918187
issue-tracking, patch, third-party-advisory
-
lists.apple.com
/archives/security-announce/2013/Sep/msg00002.html
vendor-advisory, broken-link, mailing-list
-
people.canonical.com
/~ubuntu-security/cve/2013/CVE-2013-1824.html
third-party-advisory
- git.php.net /?p=php-src.git%3Ba=commit%3Bh=188c196d4da60bdde9190d2fc532650d17f7af2d
- git.php.net /?p=php-src.git%3Ba=commit%3Bh=afe98b7829d50806559acac9b530acb8283c3bf4
-
support.apple.com
/kb/HT5880
third-party-advisory
Sources
- CVE List CVE-2013-1824
- NVD CVE-2013-1824
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.