CVE-2019-11392 json
BlogEngine.NET 3.3.7 and earlier allows XXE via an apml file to syndication.axd.
published 7y ago modified 4mo ago also EUVD-2019-3070
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
BlogEngine.NET 3.3.7 and earlier allows XXE via an apml file to syndication.axd.
Is CVE-2019-11392 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
1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- securitymetrics.com https://www.securitymetrics.com/blog/blogenginenet-xml-external-entity-attacks referenced PoC, tagged "exploit" by a source, unverified
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 |
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
securitymetrics.com
/blog/blogenginenet-xml-external-entity-attacks
exploit, third-party-advisory
Sources
- CVE List CVE-2019-11392
- NVD CVE-2019-11392
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.