CVE-2018-7654
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 · uneditedOn 3CX 15.5.6354.2 devices, the parameter "file" in the request "/api/RecordingList/download?file=" allows full access to files on the server via path traversal.
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 confidence3CX version 15.5.6354.2 contains a path traversal vulnerability in the /api/RecordingList/download endpoint. The 'file' parameter lacks proper input validation, allowing attackers to use directory traversal sequences (e.g., ../../) to read arbitrary files on the server file system.
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= 15.5.6354.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Verify 3CX installation existsCheck if 3CX software is installed on the system. On Windows, open Control Panel > Programs and Features and look for '3CX' in the installed programs list, or check the default installation directory (typically C:\Program Files\3CX\).Affected if 3CX is not installed on the system.
-
Confirm installed 3CX versionIn the 3CX Management Console, navigate to Dashboard to view the version number, or check the Windows installed programs list. Compare the version to 15.5.6354.2.Affected if The installed version is exactly 15.5.6354.2.
-
Verify web server is runningCheck if the 3CX web server is active. Typically, the management console listens on port 5000 or 443. Use a browser or curl to access the base URL (e.g., https://your-server:5000 or https://your-server).Affected if The 3CX web interface is accessible.
-
Test for vulnerable endpoint accessibilityAttempt to access the /api/RecordingList/download endpoint by sending a request to your 3CX server (e.g., curl https://your-server:5000/api/RecordingList/download). Check if the endpoint responds (even with an error).Affected if The endpoint responds with any HTTP response (200, 400, 401, etc.), indicating the API is exposed.
-
Check if file parameter accepts traversalIf the endpoint is accessible, test the vulnerability by sending a request with a directory traversal pattern in the file parameter (e.g., /api/RecordingList/download?file=../../../../windows/win.ini).Affected if The server accepts the request and returns content from outside the intended directory, confirming the path traversal vulnerability.
You are affected if 3CX version 15.5.6354.2 is installed, the web server is running, and the /api/RecordingList/download endpoint accepts directory traversal sequences in the file parameter.
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 3CX version if available. If no patch exists, implement strict input validation on the file parameter to reject traversal characters, or deploy a WAF rule to block directory traversal patterns in requests to this endpoint.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7654 — 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-7654 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