dbcve.org
Z BlogphpApplication · Zblogcn

CVE-2018-6846

MEDIUM · 5.3 CVSS v3.0 Published 2018-02-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Z-BlogPHP 1.5.1 allows remote attackers to discover the full path via a direct request to zb_system/function/lib/upload.php.

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 · high confidence

Z-BlogPHP 1.5.1 contains an information disclosure vulnerability where directly accessing zb_system/function/lib/upload.php reveals the full server file path. This occurs because the file can be invoked without proper application initialization, causing the application to output debugging or error information that exposes the absolute path on the server.

MitigationRestrict direct access to zb_system/function/lib/upload.php by adding a bootstrap check (e.g., checking for a defined constant like ZBP_INC) at the file's entry point to ensure the request goes through proper application initialization before any output occurs.

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
Z BlogphpApplication
Affected:= 1.5.1

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Z-BlogPHP version
    Check the installed version of Z-BlogPHP (typically in version.php or admin dashboard). Compare it to the affected version 1.5.1.
    Affected if The installed version is exactly 1.5.1
  2. Confirm the vulnerable file exists
    Check if zb_system/function/lib/upload.php exists in the webroot.
    Affected if The file exists in the installation
  3. Test for path disclosure
    Make a direct HTTP request to zb_system/function/lib/upload.php (e.g., GET /zb_system/function/lib/upload.php). Observe if the response contains an absolute server file path.
    Affected if Direct access returns or displays an absolute server path in error messages or output

If Z-BlogPHP 1.5.1 is installed and directly accessing zb_system/function/lib/upload.php exposes the server's absolute file path, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict direct access to zb_system/function/lib/upload.php by adding a bootstrap check (e.g., checking for a defined constant like ZBP_INC) at the file's entry point to ensure the request goes through proper application initialization before any output occurs.

Fix this in Z Blogphp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-6846 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-6846 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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