# CVE-2022-1971: NextCellent Gallery <= 1.9.35 - Admin+ Stored XSS

> Admin users can inject malicious scripts via image settings in NextCellent Gallery, leading to stored XSS in multisite environments.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-65vg-2j48-w32c

## What is CVE-2022-1971?

CVE-2022-1971 is a medium-severity cross-site scripting vulnerability in Unknown NextCellent Gallery – NextGEN Legacy, published on 27 Jun 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The NextCellent Gallery WordPress plugin through 1.9.35 does not sanitise and escape some of its image settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks when the unfiltered_html capability is disallowed (for example in multisite setup)

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

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

It affects 1 product.


Products: Wpgetready Nextcellent Gallery.

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

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

## Is CVE-2022-1971 being exploited?

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

## Other vulnerabilities in Unknown NextCellent Gallery – NextGEN Legacy

- [CVE-2014-3123](https://insights.sbomify.com/CVE-2014-3123/): Cross-site scripting in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1971 is a medium-severity cross-site scripting vulnerability in Unknown NextCellent Gallery – NextGEN Legacy, published on 27 Jun 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1971 in the wild and no public exploit code.

Affected product: Unknown NextCellent Gallery – NextGEN Legacy. 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-2022-1971/ (Markdown: https://insights.sbomify.com/CVE-2022-1971/index.md)
```

## Sources

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

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