# CVE-2022-2937: Image Hover Effects Ultimate <= 9.7.3 - Authenticated Stored Cross-Site Scripting via Title & Description

> Authenticated attackers can inject arbitrary scripts via Title and Description fields in the Image Hover Effects Ultimate plugin, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2022
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-7wq7-cmgr-8g2v

## What is CVE-2022-2937?

CVE-2022-2937 is a medium-severity cross-site scripting vulnerability in biplob018 Image Hover Effects Ultimate, published on 23 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Image Hover Effects Ultimate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Title & Description values that can be added to an Image Hover in versions up to, and including, 9.7.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. By default, the plugin only allows administrators access to edit Image Hovers, however, if a site admin makes the plugin's features available to lower privileged users through the 'Who Can Edit?' setting then this can be exploited by those users.

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

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

It affects 1 product.


Products: Oxilab Image Hover Effects Ultimate.

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

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

## Is CVE-2022-2937 being exploited?

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

## Other vulnerabilities in biplob018 Image Hover Effects Ultimate

- [CVE-2022-42459](https://insights.sbomify.com/CVE-2022-42459/): WordPress Image Hover Effects Ultimate plugin <= 9.7.1 - Auth. WordPress Options Change vulnerability (high 7.2)
- [CVE-2022-2935](https://insights.sbomify.com/CVE-2022-2935/): Image Hover Effects Ultimate <= 9.7.3 - Authenticated Stored Cross-Site Scripting via Media URL (medium 6.4)
- [CVE-2022-2936](https://insights.sbomify.com/CVE-2022-2936/): Image Hover Effects Ultimate <= 9.7.3 - Authenticated Stored Cross-Site Scripting via Video Link (medium 6.4)
- [CVE-2021-25031](https://insights.sbomify.com/CVE-2021-25031/): Image Hover Effects Ultimate < 9.7.1 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2022-4207](https://insights.sbomify.com/CVE-2022-4207/): Cross-site scripting in Image Hover Effects Ultimate (Image Gallery, Effects, Lightbox, Comparison or Magnifier) (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2937 is a medium-severity cross-site scripting vulnerability in biplob018 Image Hover Effects Ultimate, published on 23 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2937 in the wild and no public exploit code.

Affected product: biplob018 Image Hover Effects Ultimate. 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-2937/ (Markdown: https://insights.sbomify.com/CVE-2022-2937/index.md)
```

## Sources

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

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