Nuuo CmsApplication · Nuuo

CVE-2018-17936

CRITICAL · 9.8 CVSS v3.0 Published 2018-11-27
Fix available
A fix is available. Upgrade to after 3.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
NUUO CMS All versions 3.3 and prior the application allows the upload of arbitrary files that can modify or overwrite configuration files to the server, which could allow remote code execution.

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

NUUO CMS versions 3.3 and prior contains an unrestricted file upload vulnerability that allows authenticated or anonymous attackers to upload arbitrary files to the server. These uploaded files can overwrite application configuration files, enabling attackers to inject malicious code or modify settings to achieve remote code execution.

MitigationRestrict file upload functionality to validated, safe file types only (e.g., images, videos) and implement server-side validation of file content/magic bytes. Store uploaded files outside the webroot and ensure configuration files cannot be overwritten. Apply vendor patch or upgrade to a version beyond 3.3 if available.

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
Nuuo CmsApplication
Affected:<= 3.3

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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. Identify if NUUO CMS is installed
    Check for NUUO CMS web application files in the web server directory, or look for 'NUUO' or 'Nuuo' in the application name/version headers accessible via HTTP requests to the server
    Affected if NUUO CMS software is present on the server
  2. Determine the installed NUUO CMS version
    Access the CMS admin interface or check application files for version information (often in an 'about' page, config file, or footer of web pages)
    Affected if The version is 3.3 or any version lower than 3.3
  3. Verify file upload functionality is accessible
    Attempt to locate the file upload endpoint in the CMS (commonly found in add-device, add-user, or media upload features), or check if the upload form is reachable without authentication
    Affected if File upload functionality is exposed and accessible to authenticated users or anonymous users
  4. Check if uploaded files can overwrite configuration files
    Inspect the web server directory structure to determine if the upload directory is within the webroot and if uploaded files can be executed or accessed directly
    Affected if Uploaded files are stored within the web-accessible directory and configuration files (such as config.php, settings.conf, or similar) are in a writable location that could be overwritten by an upload

You are affected if NUUO CMS version 3.3 or lower is installed and the file upload feature is accessible without proper restrictions, allowing uploaded files to overwrite configuration files in the webroot.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.3
Interim mitigation

Restrict file upload functionality to validated, safe file types only (e.g., images, videos) and implement server-side validation of file content/magic bytes. Store uploaded files outside the webroot and ensure configuration files cannot be overwritten. Apply vendor patch or upgrade to a version beyond 3.3 if available.

Recommended fix Moderate confidence

NUUO CMS version 3.4 or later (contact NUUO for exact fixed release)

  1. 1. Identify the current NUUO CMS version installed by checking the application or system information.
  2. 2. Contact NUUO technical support or visit the official NUUO support website to obtain the latest version that addresses this vulnerability.
  3. 3. Before upgrading, perform a complete backup of the current NUUO CMS configuration, database, and system state.
  4. 4. Review the NUUO CMS release notes for version 3.4 or later to confirm the security fix for CVE-2018-17936 is included.
  5. 5. Execute the upgrade process following the official NUUO upgrade documentation, ensuring the system is taken offline or placed in maintenance mode during the upgrade.
  6. 6. After upgrading, verify that arbitrary file upload is no longer possible by testing with non-configuration file types.
  7. 7. If upgrading is not immediately possible, restrict administrative access to trusted IP addresses only and disable the file upload feature if possible until the upgrade can be performed.
Caveat Review NUUO release notes for any configuration or feature changes between 3.3 and the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nuuo Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-17936 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