CVE-2018-15614
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 one-x Portal component of IP Office could allow an authenticated user to perform stored cross site scripting attacks via fields in the Conference Scheduler Service that could affect other application users. Affected versions of IP Office include 10.0 through 10.1 SP3 and 11.0 versions prior to 11.0 SP1.
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 confidenceStored cross-site scripting (XSS) vulnerability in Avaya IP Office one-x Portal's Conference Scheduler Service allows authenticated users to inject malicious scripts into fields that persist and execute when viewed by other application users.
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= 10.0= 10.1= 11.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Verify Avaya IP Office one-x Portal is installedLocate the one-x Portal application on the server or check the list of installed Avaya components. Typically installed on the IP Office server under the one-x Portal directory.Affected if one-x Portal application is present on the system
-
Confirm the IP Office software versionAccess the IP Office System Status or use the IP Office Manager application to view the software version. Alternatively, check the About or version information within the one-x Portal interface.Affected if Version equals 10.0, 10.1, or 11.0
-
Determine if Conference Scheduler Service is enabledAccess the one-x Portal administrative interface and navigate to the Conference Scheduler Service configuration. Verify whether the service is active and accessible to authenticated users.Affected if Conference Scheduler Service is enabled and accessible to users
-
Inspect Conference Scheduler fields for suspicious dataUsing database queries or the administrative console, examine stored data in Conference Scheduler form fields (meeting name, description, participant fields) for HTML script tags, JavaScript event handlers, or encoded XSS payloads.Affected if Malicious script tags or XSS payloads are found stored in Conference Scheduler data fields
A user is affected if their IP Office version is 10.0, 10.1, or 11.0 AND the one-x Portal Conference Scheduler Service is enabled and accessible to authenticated users.
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 IP Office to version 10.1 SP3 or later, or 11.0 SP1 or later. Alternatively, implement input validation and output encoding on the Conference Scheduler Service fields as a compensating control until patching is possible.
- 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-2018-15614 — 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-15614 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