# CVE-2022-3000: Cross-site Scripting (XSS) - Stored in yetiforcecompany/yetiforcecrm

> Attackers can inject malicious scripts into the YetiForce CRM application, potentially compromising user sessions and data.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 20 Sep 2022
- **Updated:** 29 May 2025
- **Also known as:** GHSA-mqh9-5jp9-6799

## What is CVE-2022-3000?

CVE-2022-3000 is a medium-severity cross-site scripting vulnerability in yetiforcecompany/yetiforcecrm, published on 20 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross-site Scripting (XSS) - Stored in GitHub repository yetiforcecompany/yetiforcecrm prior to 6.4.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-3000?

2 open source packages ship an affected version, including yetiforce/yetiforce-crm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yetiforce/yetiforce-crm` | Packagist | All versions to 6.4.0 | None |
| `yetiforce/yetiforce-crm` | Packagist | All versions to 6.4.0 | None |

Products: Yetiforce Yetiforce Customer Relationship Management.

## How do I fix CVE-2022-3000?

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

## Is CVE-2022-3000 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3000 exists.

## Other vulnerabilities in yetiforcecompany/yetiforcecrm

- [CVE-2022-1411](https://insights.sbomify.com/CVE-2022-1411/): Unrestructed file upload in yetiforcecompany/yetiforcecrm (critical 9.1)
- [CVE-2022-2890](https://insights.sbomify.com/CVE-2022-2890/): Cross-site Scripting (XSS) - Stored in yetiforcecompany/yetiforcecrm (critical 9.0)
- [CVE-2022-2829](https://insights.sbomify.com/CVE-2022-2829/): Cross-site Scripting (XSS) - Stored in yetiforcecompany/yetiforcecrm (high 8.8)
- [CVE-2022-0269](https://insights.sbomify.com/CVE-2022-0269/): Cross-Site Request Forgery (CSRF) in yetiforcecompany/yetiforcecrm (high 8.0)
- [CVE-2021-4117](https://insights.sbomify.com/CVE-2021-4117/): Business Logic Errors in yetiforcecompany/yetiforcecrm (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3000 and fix it if it is affected.

What it is: CVE-2022-3000 is a medium-severity cross-site scripting vulnerability in yetiforcecompany/yetiforcecrm, published on 20 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3000 exists.

Affected packages and fixed versions:
- yetiforce/yetiforce-crm (Packagist): affected all versions up to 6.4.0; no fix listed
- yetiforce/yetiforce-crm (Packagist): affected all versions up to 6.4.0; no fix listed

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-2022-3000/ (Markdown: https://insights.sbomify.com/CVE-2022-3000/index.md)
```

## Sources

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

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