CVE-2019-5956
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 · uneditedDirectory traversal vulnerability in WonderCMS 2.6.0 and earlier allows remote attackers to delete arbitrary files via unspecified vectors.
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 · moderate confidenceWonderCMS versions 2.6.0 and earlier contain a directory traversal vulnerability that allows remote attackers to manipulate file paths and delete arbitrary files on the server via unspecified vectors. This is a path traversal issue where insufficient input validation on file operations permits '..' sequences to traverse outside the intended directory.
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<= 2.6.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 installed WonderCMS versionLocate the version file or header in the WonderCMS installation directory - typically check the main index.php file or a dedicated version file that contains the version string. Look for a version number declaration.Affected if The installed version is 2.6.0 or any version lower than 2.6.0 (e.g., 2.5.x, 2.4.x, etc.)
-
Verify web server access to file operation endpointsDetermine if the WonderCMS file management or deletion endpoints are accessible over HTTP/HTTPS. This typically involves checking if the application's file handling functions are exposed via the web interface.Affected if The file operation functionality is publicly accessible without additional authentication barriers beyond standard admin login
-
Check for presence of unrestricted file path parametersInspect the file deletion or file operation code within the WonderCMS source. Look for functions that accept file path inputs without proper validation of '..' sequences or path sanitization.Affected if The code accepts user-supplied file paths and performs operations (especially deletion) without validating that the path stays within the intended directory boundaries
-
Test for path traversal in file operationsIf you have a test environment, attempt to access a file operation function with a path containing '../' sequences (e.g., passing a path like ../../config.php to a deletion function). In a production environment, review access logs for patterns of '..' in file-related requests.Affected if The application allows path traversal sequences ('..') to traverse outside the designated upload or working directory and perform operations on files outside that scope
A user is affected if WonderCMS version 2.6.0 or earlier is installed AND the file operation functionality is accessible, allowing path traversal sequences to delete files outside the intended directory.
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.
From vendor dataUpgrade WonderCMS to a version newer than 2.6.0 which contains the patched code. If immediate patching is not feasible, implement strict input validation on all file path parameters and ensure web server processes have minimal file system permissions to limit the impact of exploitation.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5956 — 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-2019-5956 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