Security readout for executives and security teams
Plain-English summary
b3log Wide versions before 1.6.0 could let an attacker reach files outside the intended workspace. The reported paths involve editor code execution and symlink handling in ZIP or Git import workflows. Business impact depends on what files the Wide process can read or write.
Executive priority
Prioritize if Wide is internet-accessible, shared with untrusted users, or runs with broad file permissions. The main concern is unauthorized access to sensitive local files, with possible writes depending on permissions.
Technical view
The CVE describes arbitrary file access in b3log Wide before 1.6.0 via three mechanisms: repeated editor compile/run activity, ZIP extraction involving symlinks, and Git repository import containing symlinks. Write access may also be possible depending on filesystem permissions. Sources do not provide CVSS, CWE, or authentication requirements.
Likely exposure
Exposure is likely limited to environments running b3log Wide before 1.6.0, especially where users can access the editor, ZIP extraction, or Git import features. The source bundle does not identify affected CPEs or deployment patterns.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The described attack paths require interaction with Wide features, but the sources do not say whether authentication or specific privileges are required.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, exploit status, or authentication details are supplied. The strongest technical signal is the CVE description and linked GitHub issue. Treat the version boundary and three file-access vectors as the validated scope.
Mitigation direction
- Upgrade b3log Wide to 1.6.0 or later where applicable.
- Check the upstream GitHub issue and vendor guidance for confirmed fixes.
- Restrict access to editor, ZIP import, and Git import features.
- Run Wide with least-privilege filesystem permissions.
- Review workspace and extraction handling for symlink exposure.
Validation and detection
- Inventory deployed b3log Wide versions and flag versions before 1.6.0.
- Confirm whether editor compile/run functionality is exposed to untrusted users.
- Confirm whether ZIP extraction and Git import are enabled.
- Review process filesystem permissions for sensitive read or write reach.
- Check logs for unexpected imports, archives, or file access patterns.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-13915 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/b3log/wide/issues/355CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
