WideApplication · Wide Project
CVE-2020-19279
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDirectory Traversal vulnerability found in B3log Wide allows a an attacker to escalate privileges via symbolic links.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA directory traversal vulnerability in B3log Wide allows attackers to escalate privileges by exploiting symbolic links. The vulnerability enables traversal outside intended directory boundaries through maliciously crafted symlink references.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
WideApplication
all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if B3log Wide is installedSearch for Wide application files, processes, or services on the system. Look for executables named 'wide', 'b3log-wide', or check running processes for wide-related entries.Affected if B3log Wide software is found running or installed on the system
-
Check configuration for symlink handling settingsExamine the Wide configuration files (typically in config/ or conf/ directories) for settings related to symbolic link processing, path resolution, or file access controls.Affected if Symlink following is enabled or no path validation controls are configured
-
Verify file operation endpointsInspect the application's file handling code or API endpoints that accept file paths. Look for functions that perform file reads, writes, or directory listings without resolving symlinks.Affected if File operations accept user-controlled paths without validating symbolic link resolution
-
Test symlink behavior in file operationsCreate a symbolic link pointing outside the intended directory and attempt to access it through the application's file handling functionality. Observe if the link is followed to traverse directories.Affected if The application follows symbolic links and allows access outside intended directory boundaries
-
Review logging for traversal attemptsCheck application logs for any symlink-related errors, path validation failures, or unusual file access patterns that may indicate exploitation attempts.Affected if Logs show symlink resolution occurring without proper validation
The environment is affected if B3log Wide is installed and the application processes file paths without resolving or validating symbolic links before operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict path validation that resolves and validates all symbolic links before file operations, restrict symlink following, and enforce allowlist-based path controls.
Fix this in Wide
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-19279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-19279 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data