# CVE-2023-31187: Avaya IX Workforce Engagement - CWE-522: Insufficiently Protected Credentials

> Attackers can access sensitive data or take over accounts due to insufficiently protected credentials in Avaya IX Workforce Engagement.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-57hv-vqrf-h67f

## What is CVE-2023-31187?

CVE-2023-31187 is a medium-severity vulnerability in Avaya IX Workforce Engagement, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Avaya IX Workforce Engagement v15.2.7.1195 - CWE-522: Insufficiently Protected Credentials

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2023-31187?

It affects 1 product.


Products: Avaya Ix Workforce Engagement.

## How do I fix CVE-2023-31187?

No fix has been published for CVE-2023-31187 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-31187 being exploited?

There is no known exploitation of CVE-2023-31187 in the wild and no public exploit code.

## Other vulnerabilities in Avaya IX Workforce Engagement

- [CVE-2023-32218](https://insights.sbomify.com/CVE-2023-32218/): Avaya IX Workforce Engagement - CWE-601: URL Redirection to Untrusted Site ('Open Redirect') (medium 6.1)
- [CVE-2023-31186](https://insights.sbomify.com/CVE-2023-31186/): Avaya IX Workforce Engagement - User Enumeration - CWE-204: Observable Response Discrepancy (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31187 and fix it if it is affected.

What it is: CVE-2023-31187 is a medium-severity vulnerability in Avaya IX Workforce Engagement, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31187 in the wild and no public exploit code.

Affected product: Avaya IX Workforce Engagement. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-31187/ (Markdown: https://insights.sbomify.com/CVE-2023-31187/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-31187
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-31187
- OSV: https://osv.dev/vulnerability/CVE-2023-31187

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-31187/
Summaries are generated and may contain mistakes; the official description above is the record.