# CVE-2022-4763: Icon Widget < 1.3.0 - Contributor+ Stored XSS via Shortcode

> Contributors can inject malicious scripts via shortcode attributes in the Icon Widget plugin, potentially compromising admin accounts.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 30 Jan 2023
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-pf73-wv46-5h3f

## What is CVE-2022-4763?

CVE-2022-4763 is a medium-severity cross-site scripting vulnerability in Unknown Icon Widget, published on 30 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Icon Widget WordPress plugin before 1.3.0 does not validate and escape some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks which could be used against high privilege users such as admins.

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

It affects 1 product.


Products: Wpzoom Icon Widget.

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

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

## Is CVE-2022-4763 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4763 is a medium-severity cross-site scripting vulnerability in Unknown Icon Widget, published on 30 Jan 2023. 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-4763 in the wild and no public exploit code.

Affected product: Unknown Icon Widget. 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-4763/ (Markdown: https://insights.sbomify.com/CVE-2022-4763/index.md)
```

## Sources

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

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