CVE-2018-5781
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 · uneditedA vulnerability in the conferencing component of Mitel Connect ONSITE, versions R1711-PREM and earlier, and Mitel ST 14.2, release GA28 and earlier, could allow an unauthenticated attacker to inject PHP code using specially crafted requests to the vendrecording.php page. Successful exploit could allow an attacker to execute arbitrary PHP code within the context of the application.
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 confidenceAn unauthenticated PHP code injection vulnerability in the vende recording.php page of the Mitel Connect ONSITE and Mitel ST conferencing components allows remote attackers to execute arbitrary PHP code within the application context without authentication.
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<= r1711-prem<= ga28CVSS 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 Mitel conferencing software installationLocate the Mitel Connect ONSITE or Mitel ST installation directory on the server, typically found in the web server root or application directory.Affected if The software is installed and the version cannot be determined or is at or below r1711-prem (ONSITE) or ga28 (ST14.2)
-
Determine the installed versionCheck the application version information in the product itself, typically accessible through the admin interface or in version files within the installation directory.Affected if The installed version is Mitel Connect Onsite <= r1711-prem or Mitel ST14.2 <= ga28
-
Verify recording.php is web-accessibleAttempt to access the recording.php page via HTTP/HTTPS from the web server hosting the conferencing component (e.g., https://yourserver/path/recording.php).Affected if The recording.php page responds without requiring authentication, indicating it is exposed and potentially exploitable
-
Check for unauthorized access attemptsReview web server access logs and application logs for suspicious requests to recording.php that may contain PHP code injection payloads.Affected if Log entries show unauthenticated requests to recording.php containing PHP code patterns (e.g., system(), exec(), passthru(), shell_exec())
The environment is affected if Mitel Connect Onsite version r1711-prem or earlier, or Mitel ST14.2 version ga28 or earlier is installed AND the recording.php page is accessible without authentication.
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 dataApply vendor-supplied patches/updates: upgrade Mitel Connect ONSITE beyond version R1711-PREM and Mitel ST beyond release GA28. If patches are unavailable, disable or restrict access to the conferencing component as a compensating control.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5781 — 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-5781 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