Skip to content
Fencer Intel
critical 9.8

CVE-2018-17888 in the critical feed json

NUUO CMS all versions 3.1 and prior, The application uses a session identification mechanism that could allow attackers to obtain the activ…

published 8y ago modified 4mo ago also EUVD-2018-9629

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
29.6%
EPSS 29.6% chance of exploitation in 30 days, percentile 98%
public exploits
1
Metasploit

Summary

NUUO CMS all versions 3.1 and prior, The application uses a session identification mechanism that could allow attackers to obtain the active session ID, which could allow arbitrary remote code execution.

Patch / fix

Is CVE-2018-17888 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-18-284-02 updated cvss 9.8

NUUO CMS (Update A)

  • NUUO CMS <= 3.3, <= 3.1
    affected: mitigation “NUUO has developed a fix for the reported vulnerabilities and recommends users update to firmware v3.3 or the latest available.”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. First public exploit (Metasploit auxiliary/gather/nuuo_cms_bruteforce)
  2. Published

Exploit prediction

29.64% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • NUUO NUUO CMS

Classification

Weakness
  • CWE-330 Use of Insufficiently Random Values

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.