CVE-2018-11209

CVE-2018-11209 is a high-severity vulnerability in Zblogcn Z-blogphp with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Description

An issue was discovered in Z-BlogPHP 2.0.0. zb_system/cmd.php?act=verify relies on MD5 for the password parameter, which might make it easier for attackers to bypass intended access restrictions via a dictionary or rainbow-table attack. NOTE: the vendor declined to accept this as a valid issue

Frequently asked questions

What is CVE-2018-11209?
An issue was discovered in Z-BlogPHP 2.0.0. zb_system/cmd.php?act=verify relies on MD5 for the password parameter, which might make it easier for attackers to bypass intended access restrictions via a dictionary or rainbow-table attack. NOTE: the vendor declined to accept this as a valid issue
How severe is CVE-2018-11209?
CVE-2018-11209 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-11209 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-11209?
CVE-2018-11209 affects Zblogcn Z-blogphp. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-11209?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-11209 published?
CVE-2018-11209 was published on 2018-05-16 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Zblogcn Z-blogphp

All CVEs affecting Zblogcn Z-blogphp →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →