dbcve.org
Z BlogphpApplication · Zblogcn

CVE-2018-9153

HIGH · 7.2 CVSS v3.0 Published 2018-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
The plugin upload component in Z-BlogPHP 1.5.1 allows remote attackers to execute arbitrary PHP code via the app_id parameter to zb_users/plugin/AppCentre/plugin_edit.php because of an unanchored regular expression, a different vulnerability than CVE-2018-8893. The component must be accessed directly by an administrator, or through CSRF.

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 arbitrary PHP code execution vulnerability in the plugin upload component. The app_id parameter in zb_users/plugin/AppCentre/plugin_edit.php uses an unanchored regular expression, allowing attackers to inject malicious code. Exploitation requires administrator access or can be achieved via CSRF attack.

MitigationUpgrade to a patched version of Z-BlogPHP. If immediate patching is not possible, restrict administrative access to trusted users and implement CSRF tokens on all administrative actions.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/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 checks

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

  1. Check Z-BlogPHP version installed
    Log into the admin panel and navigate to the version information page, or inspect the version file in the Z-BlogPHP installation directory. The version is typically displayed in the site footer of the admin dashboard or stored in a version.php or version.json file at the root of the installation.
    Affected if The installed version is exactly 1.5.1. Note that this vulnerability may also affect versions if the codebase was modified or if the vendor confirmed additional versions - compare your version against the affected range provided by the vendor.
  2. Verify AppCentre plugin file exists
    Check if the file zb_users/plugin/AppCentre/plugin_edit.php exists in the web root of the Z-BlogPHP installation. Use file system access or a directory listing to confirm the presence of this specific path.
    Affected if The file zb_users/plugin/AppCentre/plugin_edit.php exists on the server. If this file does not exist, the specific vulnerable component is not present.
  3. Confirm AppCentre plugin is enabled
    Log into the Z-BlogPHP admin panel and navigate to the plugin management area. Check whether the AppCentre (or Application Centre) plugin is installed and activated. Alternatively, check if the plugin directory contains the active plugin configuration.
    Affected if The AppCentre plugin is installed and enabled in the Z-BlogPHP installation. The vulnerability only applies when this plugin component is active.
  4. Check access to plugin edit functionality
    Verify whether the plugin_edit.php file is accessible via the web by attempting to access the URL path /zb_users/plugin/AppCentre/plugin_edit.php or checking web server access logs for requests to this endpoint.
    Affected if The plugin_edit.php file is web-accessible. Exploitation requires either direct administrative access or tricking an administrator into performing a CSRF request.

You are affected if your Z-BlogPHP version is exactly 1.5.1, the AppCentre plugin is enabled, and the vulnerable plugin_edit.php file is present and accessible on your server.

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

Upgrade to a patched version of Z-BlogPHP. If immediate patching is not possible, restrict administrative access to trusted users and implement CSRF tokens on all administrative actions.

Fix this in Z Blogphp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-9153 — 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-9153 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