Is yetiforce/yetiforce-crm vulnerable?

Composer yetiforce/yetiforce-crm has 17 known advisories in the phpwarden feed. Feed 2026.10.29.4, updated 2026-10-29.

17advisories
0critical
0on CISA KEV
11no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2023-49508YetiForceCRM Directory Traversal vulnerabilitymedium6.5<6.5.06.5.0
CVE-2022-2890Cross site scripting in yetiforce/yetiforce-crmmedium5.4<6.4.06.4.0
CVE-2021-4107yetiforcecrm is vulnerable to Cross-site Scriptingmedium5.3<=6.3.0–
CVE-2021-4121yetiforcecrm is vulnerable to Cross-site Scriptingmedium6.4<=6.3.0–
CVE-2022-2924YetiForce CRM vulnerable to stored Cross-site Scripting via WidgetsManagement modulemedium5.4<=6.4.0–
CVE-2022-1411Unrestricted Upload of File with Dangerous Type in yetiforce-crmmedium6.1<6.4.06.4.0
CVE-2021-4117YetiForceCRM is vulnerable to Business Logic Errors in the weight of a productmedium4.3<=6.3.0–
CVE-2022-3002YetiForce CRM vulnerable to stored Cross-site Scriptingmedium5.4<=6.4.0–
CVE-2022-3000YetiForce CRM vulnerable to stored Cross-site Scripting via LayoutEditor modulemedium5.4<=6.4.0–
CVE-2022-3004YetiForce CRM vulnerable to stored Cross-site Scripting via WorkFlow modulemedium5.4<=6.4.0–
CVE-2022-3005YetiForce CRM vulnerable to stored Cross-site Scripting via SlaPolicy modulemedium5.4<=6.4.0–
CVE-2021-4111YetiForceCRM is vulnerable to Business Logic Errors because product amount can be a negative numberhigh7.3<=6.3.0–
CVE-2022-0269Cross-Site Request Forgery in yetiforcehigh8.0<=6.3.0–
CVE-2022-1340Cross site scripting in yetiforce/yetiforce-crmmedium5.4<6.4.06.4.0
CVE-2022-2885Cross site scripting in yetiforce/yetiforce-crmmedium4.8<6.4.06.4.0
CVE-2021-4116yetiforcecrm is vulnerable to Cross-site Scriptingmedium6.6<=6.3.0–
CVE-2021-4092yetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF)medium4.3<6.3.06.3.0

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.