CVE-2015-5650
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 AjaXplorer 2.0 allows remote attackers to read 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 confidenceDirectory traversal vulnerability in AjaXplorer 2.0 allows remote attackers to read arbitrary files on the server by manipulating file path parameters using '..' sequences or absolute paths to access files outside the intended web root 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.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 AjaXplorer installationLocate the AjaXplorer web application directory on the server. Common paths include /var/www/html/ajaxplorer, /www/ajaxplorer, or similar web root locations. Look for the main index.php file and conf/registry.xml configuration file.Affected if AjaXplorer is present in the web directory structure
-
Determine installed versionOpen the conf/VERSION or conf/bootstrap_conf.php file within the AjaXplorer installation directory and read the version number stated in the file.Affected if The version reads exactly 2.0 or falls within an unpatched version range
-
Verify web interface accessibilityCheck if the AjaXplorer web interface is reachable over HTTP/HTTPS by accessing the installation URL (e.g., http://yourserver/ajaxplorer). Confirm the application responds and loads.Affected if The web interface is accessible over the network
-
Test for path traversal vulnerabilitySend a crafted HTTP request to the file browsing endpoint with a path parameter containing '../' sequences or an absolute path such as '/etc/passwd'. For example: http://yourserver/ajaxplorer/?action=get_content&file=../../../../etc/passwd or use the file browser API to request a path outside the intended repository.Affected if The server returns file contents from outside the allowed directory (e.g., /etc/passwd or other system files)
A user is affected if AjaXplorer version 2.0 is installed and its web interface allows path traversal to read files outside the intended directory boundaries.
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 to a patched version of AjaXplorer. If immediate patching is not possible, implement strict input validation on all file path parameters, sanitize path traversal sequences ('..'), and restrict the application to access only designated directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5650 — 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-2015-5650 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