# DRUPAL-CORE-2022-001: jQuery UI is a third-party library used by Drupal. > Cross-site scripting vulnerability in jQuery UI library used by Drupal allows attackers to inject malicious scripts via the position utility. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 19 Jan 2022 ## What is DRUPAL-CORE-2022-001? DRUPAL-CORE-2022-001 is a cross-site scripting vulnerability in drupal/core, published on 19 Jan 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description jQuery UI is a third-party library used by Drupal. This library was previously thought to be end-of-life. Late in 2021, jQuery UI announced that they would be continuing development, and released a [jQuery UI 1.13.0](https://blog.jqueryui.com/2021/10/jquery-ui-1-13-0-released/) version. As part of this 1.13.0 update, they disclosed the following security issue that may affect Drupal 9 and 7: * CVE-2021-41184: [XSS in the `of` option of the `.position()` util](https://github.com/jquery/jquery-ui/security/advisories/GHSA-gpqq-952q-5327) It is possible that this vulnerability is exploitable with some Drupal modules. As a precaution, this Drupal security release applies the fix for the above cross-site description issue, without making any of the other changes to the jQuery version that is included in Drupal. This advisory is not covered by [Drupal Steward](/steward). ## Which versions are affected by DRUPAL-CORE-2022-001? 1 open source package ship an affected version, including drupal/core. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `drupal/core` | Packagist | From 8.0.0 | 9.2.11, 9.3.3 | ## How do I fix DRUPAL-CORE-2022-001? Upgrade drupal/core to a fixed version for your release line: 9.2.11 or 9.3.3. ## Is DRUPAL-CORE-2022-001 being exploited? There is no known exploitation of DRUPAL-CORE-2022-001 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for DRUPAL-CORE-2022-001 and fix it if it is affected. What it is: DRUPAL-CORE-2022-001 is a cross-site scripting vulnerability in drupal/core, published on 19 Jan 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of DRUPAL-CORE-2022-001 in the wild and no public exploit code. Affected packages and fixed versions: - drupal/core (Packagist): affected from 8.0.0; fixed in 9.2.11, 9.3.3 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/DRUPAL-CORE-2022-001/ (Markdown: https://insights.sbomify.com/DRUPAL-CORE-2022-001/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/DRUPAL-CORE-2022-001 --- From sbomify Insights: https://insights.sbomify.com/DRUPAL-CORE-2022-001/ Summaries are generated and may contain mistakes; the official description above is the record.