# CVE-2022-35501: Cross-site scripting in n/a

> Stored XSS in Amasty Blog Pro allows attackers to inject scripts via duplicate posts, potentially compromising user sessions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Nov 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-354v-mvpg-vvr4

## What is CVE-2022-35501?

CVE-2022-35501 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Stored Cross-site Scripting (XSS) exists in the Amasty Blog Pro 2.10.3 and 2.10.4 plugin for Magento 2 because of the duplicate post function.

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

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

It affects 1 product.


Products: Amasty Blog Pro.

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

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

## Is CVE-2022-35501 being exploited?

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

Public exploit code:

- Stored Cross-site Scripting (XSS) in blog-post creation functionality in Amasty Blog Pro for Magento 2 (github_poc): https://github.com/afine-com/CVE-2022-35501

## Other vulnerabilities in n/a

- [CVE-2022-35500](https://insights.sbomify.com/CVE-2022-35500/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2022-36432](https://insights.sbomify.com/CVE-2022-36432/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-35501 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-35501 in the wild and no public exploit code.

Affected product: n/a. 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-35501/ (Markdown: https://insights.sbomify.com/CVE-2022-35501/index.md)
```

## Sources

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

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