CVE-2022-0274 is a medium-severity (CVSS 6.8) Cross-site Scripting (XSS) vulnerability in OrchardCore.Application.Cms.Targets. 1 public exploit reference exists, so weaponization risk is real. A fix is available for OrchardCore.Application.Cms.Targets — see the affected versions and patch details below.
Cross-site Scripting (XSS) - Stored in orchardcms/orchardcore
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-0274 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
OrchardCore.Application.Cms.TargetsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Cross-site Scripting (XSS) - Stored in NuGet OrchardCore.Application.Cms.Targets prior to 1.2.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | OrchardCore.Application.Cms.Targets | all versions | 1.2.2dotnet add package OrchardCore.Application.Cms.Targets --version 1.2.2 |
Affected Products
orchardcoreorchardcoreResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OrchardCore.Application.Cms.Targets, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update OrchardCore.Application.Cms.Targets to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0274 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2022-0274 in your dependencies?
Find it across NuGet, including transitive dependencies.