CVE-2014-8704
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 index.php in Wonder CMS 2014 allows remote attackers to include and execute arbitrary local files via a crafted theme.
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 confidenceA directory traversal vulnerability in index.php of Wonder CMS 2014 allows remote attackers to include and execute arbitrary local files via a crafted theme parameter, enabling remote code execution.
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= 2014CVSS 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 Wonder CMS installationSearch for the presence of index.php and verify it is part of Wonder CMS by checking for the Wonder CMS branding or file structure.Affected if The application is Wonder CMS version 2014
-
Verify the installed versionOpen index.php or check a version file within the Wonder CMS directory to confirm the version is exactly 2014.Affected if The installed version is exactly 2014
-
Check if theme parameter is accessibleInspect index.php source code to locate the theme parameter handling logic and determine if it can be controlled via HTTP request parameters.Affected if The theme parameter is processed from user input without validation
-
Confirm web-facing exposureDetermine if the vulnerable index.php is accessible over HTTP/HTTPS to remote attackers.Affected if The index.php is accessible via the web and accepts theme parameter input
If Wonder CMS version 2014 is installed and its index.php is web-accessible with a user-controllable theme parameter, the environment is affected by CVE-2014-8704.
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 and sanitization on the theme parameter to block directory traversal sequences (../) and use an allowlist of permitted theme names.
Latest stable Wonder CMS version (post-2014)
- 1. Backup your current Wonder CMS installation and database before making any changes
- 2. Navigate to the official Wonder CMS website or repository to obtain the latest stable version
- 3. Download the most recent version of Wonder CMS that addresses the directory traversal vulnerability
- 4. Replace the existing index.php file with the updated version from the new release
- 5. Verify that theme parameter handling in index.php no longer allows directory traversal (e.g., ensure proper sanitization of '../' sequences)
- 6. Test the updated installation by attempting to access files outside the web root via theme parameter
- 7. Restore your data from the backup and verify functionality
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2014-8704 — 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-2014-8704 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