CVE-2015-5161: The Zend_Xml_Security::scan in ZendXml before 1.0.1 and Zend Framework before 1.12.14, 2.x before 2.4.6, and 2.5.x before 2.5.2, when…
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 9.8% (FIRST EPSS); higher than 95.6% of all records.
- Fixed version: zendframework (Debian:6.0) 1.10.6-1squeeze5; zendframework (Debian:7) 1.11.13-1.1+deb7u3; zendframework (Debian:8) 1.12.9+dfsg-2+deb8u3.
Low priority for now. Upgrade to zendframework (Debian:6.0) 1.10.6-1squeeze5; zendframework (Debian:7) 1.11.13-1.1+deb7u3; zendframework (Debian:8) 1.12.9+dfsg-2+deb8u3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The Zend_Xml_Security::scan in ZendXml before 1.0.1 and Zend Framework before 1.12.14, 2.x before 2.4.6, and 2.5.x before 2.5.2, when running under PHP-FPM in a threaded environment, allows remote attackers to bypass security checks and conduct XML external entity (XXE) and XML entity expansion (XEE) attacks via multibyte encoded characters.
- Published
- Aug 25, 2015
- Updated
- Jun 16, 2026
- EPSS
- 9.8% · 95th percentile
- CWE
- —
Report tools
Action score
30
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zend | zend framework | cpe:2.3:a:zend:zend_framework |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zend zend framework1.0.0
- zend zend framework1.0.1
- zend zend framework1.0.2
- zend zend framework1.0.3
- zend zend framework1.0.4
- zend zend framework1.10.0
- zend zend framework1.10.1
- zend zend framework1.10.2
+12 more rows
- zend zend framework1.10.3
- zend zend framework1.10.4
- zend zend framework1.10.5
- zend zend framework1.10.6
- zend zend framework1.10.7
- zend zend framework1.10.8
- zend zend framework1.10.9
- zend zend framework1.11.0
- zend zend framework1.11.1
- zend zend framework1.11.10
- zend zend framework1.11.11
- zend zend framework1.11.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:6.0 | zendframework | before 1.10.6-1squeeze5 | 1.10.6-1squeeze5 |
| Debian:7 | zendframework | before 1.11.13-1.1+deb7u3 | 1.11.13-1.1+deb7u3 |
| Debian:8 | zendframework | before 1.12.9+dfsg-2+deb8u3 | 1.12.9+dfsg-2+deb8u3 |
| Packagist | zendframework/zendframework | from 1.12.0 · before 1.12.14 | 1.12.14 |
| Packagist | zendframework/zendframework | from 2.0.0 · before 2.4.6 | 2.4.6 |
| Packagist | zendframework/zendframework | from 2.5.0 · before 2.5.2 | 2.5.2 |
| Packagist | zendframework/zendframework1 | from 1.12.0 · before 1.12.14 | 1.12.14 |
| Packagist | zendframework/zendxml | from 1.0.0 · before 1.0.1 | 1.0.1 |
Same product
zend: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3007Laminas Project laminas-http before 2.14.2, and Zend Framework 3.0.0, has a deserialization vulnerability that can lead to remote code…62This week
- CVE-2016-10034The setFrom function in the Sendmail adapter in the zend-mail component before 2.4.11, 2.5.x, 2.6.x, and 2.7.x before 2.7.2, and Zend…51Plan
- CVE-2012-3363Zend_XmlRpc in Zend Framework 1.x before 1.11.12 and 1.12.x before 1.12.0 does not properly handle SimpleXMLElement classes, which allows…51Plan
Published before and after this one in the same product
- ← EarlierCVE-2014-2685Sep 4, 2014 · The GenericConsumer class in the Consumer component in ZendOpenId before 2.0.2 and the Zend_OpenId_Consumer class in Zend Framework 1…31Monitor
- ← EarlierCVE-2014-8088Oct 22, 2014 · The (1) Zend_Ldap class in Zend before 1.12.9 and (2) Zend\Ldap component in Zend 2.x before 2.2.8 and 2.3.x before 2.3.3 allows remote…21Monitor
- Later →CVE-2015-7695Jun 7, 2016 · The PDO adapters in Zend Framework before 1.12.16 do not filer null bytes in SQL statements, which allows remote attackers to execute…40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:zendframework | 1.10.6-1squeeze5 · Debian:6.0 | Package registry (OSV) |
| Packagist:zendframework/zendframework | 1.12.14 | Package registry (OSV) |
| Packagist:zendframework/zendframework | 2.4.6 | Package registry (OSV) |
| Packagist:zendframework/zendframework | 2.5.2 | Package registry (OSV) |
| Packagist:zendframework/zendframework1 | 1.12.14 | Package registry (OSV) |
| Packagist:zendframework/zendxml | 1.0.1 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2015-08-13 |
| Exploit-DB entry | webapps | 2015-10-30 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-13 d
- Published
- TodayNov 16, 2026+4101 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
—
CVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.