# CVE-2023-2026: Image Protector <= 1.1 - Admin+ Stored Cross-Site Scripting

> High-privilege users can inject malicious scripts via unsanitized settings in the Image Protector plugin, potentially compromising other users.

- **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:** 10 Jul 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-grpp-v27v-jff6

## What is CVE-2023-2026?

CVE-2023-2026 is a medium-severity cross-site scripting vulnerability in Unknown Image Protector, published on 10 Jul 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Image Protector WordPress plugin through 1.1 does not properly sanitize some of its settings, which could allow high-privilege users to perform Stored Cross-Site Scripting (XSS) attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

## Which versions are affected by CVE-2023-2026?

It affects 1 product.


Products: Image Protector Project Image Protector.

## How do I fix CVE-2023-2026?

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

## Is CVE-2023-2026 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2026 and fix it if it is affected.

What it is: CVE-2023-2026 is a medium-severity cross-site scripting vulnerability in Unknown Image Protector, published on 10 Jul 2023. 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-2023-2026 in the wild and no public exploit code.

Affected product: Unknown Image Protector. 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-2023-2026/ (Markdown: https://insights.sbomify.com/CVE-2023-2026/index.md)
```

## Sources

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

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