# CVE-2022-44586: WordPress AM-HiLi plugin <= 1.0 - Auth. Stored Cross-Site Scripting (XSS) vulnerability

> Authenticated administrators can inject malicious scripts into the AM-HiLi WordPress plugin, potentially leading to session hijacking or site compromise.

- **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:** 2 Nov 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-55c5-p398-pq29

## What is CVE-2022-44586?

CVE-2022-44586 is a medium-severity cross-site scripting vulnerability in Ayoub Media AM-HiLi (WordPress plugin), published on 2 Nov 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Auth. (admin+) Stored Cross-Site Scripting (XSS) in Ayoub Media AM-HiLi plugin <= 1.0 on WordPress.

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

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

It affects 1 product.


Products: Am-Hili Project Am-Hili.

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

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

## Is CVE-2022-44586 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44586 is a medium-severity cross-site scripting vulnerability in Ayoub Media AM-HiLi (WordPress plugin), published on 2 Nov 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-44586 in the wild and no public exploit code.

Affected product: Ayoub Media AM-HiLi (WordPress plugin). 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-44586/ (Markdown: https://insights.sbomify.com/CVE-2022-44586/index.md)
```

## Sources

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

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