CVE-2018-17934
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 · uneditedNUUO CMS All versions 3.3 and prior the application allows external input to construct a pathname that is able to be resolved outside the intended directory. This could allow an attacker to impersonate a legitimate user, obtain restricted information, or execute arbitrary code.
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 confidenceNUUO CMS versions 3.3 and prior contains a path traversal vulnerability where external input is used to construct file paths that can resolve outside the intended directory, potentially allowing attackers to access arbitrary files, impersonate legitimate users, or execute arbitrary code.
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<= 3.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify NUUO CMS versionAccess the NUUO CMS web interface login page or check system information/About section to find the installed software version numberAffected if The version displayed is 3.3 or any version lower than 3.3
-
Confirm web application is exposedVerify the NUUO CMS web interface (typically on port 80 or 443) is accessible from networkAffected if The web interface responds and is accessible over HTTP/HTTPS
-
Locate the PHP handler filesOn the NUUO CMS server, search for PHP files in the web root directory that handle file path parameters, typically in /NUUO/ or similar application directoriesAffected if PHP files exist that process file path parameters without proper validation
-
Check file upload functionalityIdentify if the web application contains file upload or file download features that accept file path parameters from user inputAffected if File upload, download, or file handling features are present and accessible to users
-
Test for path traversal vulnerabilityIf you have authorized access, send a crafted request with ../ sequences in file path parameters (e.g., ../../../etc/passwd) to identified endpoints and observe if the application returns files outside the intended directoryAffected if The application returns content from files outside the designated web root directory when ../ sequences are used
A system is affected if NUUO CMS version 3.3 or lower is installed and the web interface with file handling features is accessible, allowing path traversal via user-supplied file path parameters.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement strict input validation with allowlist approach for file path parameters, apply proper path canonicalization to resolve symlinks and relative paths, and enforce filesystem access controls following principle of least privilege.
NUUO CMS v3.4 or later
- 1. Identify the current installed version of NUUO CMS
- 2. Back up all configuration files and database
- 3. Download NUUO CMS version 3.4 or later from the official vendor
- 4. Stop the NUUO CMS service
- 5. Install the upgraded version following vendor documentation
- 6. Restart the service and verify functionality
- 7. Change all administrative passwords after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,208.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17934 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-17934 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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