CVE-2018-16239

CRITICALNVD 9.8

9.8

An issue was discovered in damiCMS V6.0.1. It relies on the PHP time() function for cookies, which makes it possible to determine the cookie for an existing admin session via 10800 guesses.

CVSS v3: 9.8
EG Score: —
EPSS: 62.0%
KEV: Not listed

Published

August 30, 2018

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated May 26, 2026

No patch confirmed yet.

generic

Get a damiCMS‘s admin permission by Force authentication · Issue #2 · howchen/howchen · GitHub

https://github.com/howchen/howchen/issues/2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-330Use of Insufficiently Random Values

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2018-16239?

CVE-2018-16239 is a critical vulnerability published on August 30, 2018. An issue was discovered in damiCMS V6.0.1. It relies on the PHP time() function for cookies, which makes it possible to determine the cookie for an existing admin session via 10800 guesses.

When was CVE-2018-16239 disclosed?

CVE-2018-16239 was first published in the National Vulnerability Database on August 30, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-16239 actively exploited?

CVE-2018-16239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 62.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-16239?

CVE-2018-16239 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2018-16239?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-16239, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-16239

Explore →

Is Your Infrastructure Affected by CVE-2018-16239?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs