PatchTheCVEdotnetblogengine vulnerabilities
Recent CVEs affecting dotnetblogengine products. 5 tracked.
dotnetblogengine has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2019-07-03. Highest priority: CVE-2019-10719 (score 59/100).
- CVE-2019-11392 HIGH 7.5 UPGRADE BlogEngine.NET 3.3.7 and earlier allows XXE via an apml file to syndication.axd.
- CVE-2019-10721 MEDIUM 6.1 DOWNGRADE BlogEngine.NET 3.3.7.0 allows a Client Side URL Redirect via the ReturnUrl parameter, related to BlogEngine/Bl
- CVE-2019-10719 HIGH 8.8 UPGRADE BlogEngine.NET 3.3.7.0 and earlier allows Directory Traversal and Remote Code Execution because file creation
- CVE-2019-10718 HIGH 7.5 UPGRADE BlogEngine.NET 3.3.7.0 and earlier allows XML External Entity Blind Injection, related to pingback.axd and Blo
- CVE-2019-10717 HIGH 7.1 DOWNGRADE BlogEngine.NET 3.3.7.0 allows /api/filemanager Directory Traversal via the path parameter.
FAQ
How do I fix dotnetblogengine vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is dotnetblogengine being exploited right now?
None of the tracked dotnetblogengine CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which dotnetblogengine CVE should I patch first?
CVE-2019-10719 currently ranks highest (59/100): BlogEngine.NET 3.3.7.0 and earlier allows Directory Traversal and Remote Code Execution because file creation .