CVE-2019-12277 is a critical-severity (CVSS 9.8) Path Traversal vulnerability in Blogifier.Core. A fix is available for Blogifier.Core — see the affected versions and patch details below.
Blogifier does not properly restrict APIs
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
Blogifier.CoreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Blogifier 2.3 before 2019-05-11 does not properly restrict APIs, as demonstrated by missing checks for .. in a pathname.
The issue is patched in the 2.4 branch, but 2.5.5 is the lowest available patched version on https://www.nuget.org/packages/Blogifier.Core.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Blogifier.Core | all versions | 2.5.5dotnet add package Blogifier.Core --version 2.5.5 |
Affected Products
blogifierblogifierDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Blogifier.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Blogifier.Core to 2.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12277 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2019-12277 in your dependencies?
Find it across NuGet, including transitive dependencies.