# CVE-2022-35698: Adobe Commerce Stored XSS Arbitrary code execution

> Stored XSS in Adobe Commerce allows post-authentication arbitrary code execution without user interaction.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-4vj2-426r-jm3g

## What is CVE-2022-35698?

CVE-2022-35698 is a critical cross-site scripting vulnerability in Adobe Commerce, published on 14 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Adobe Commerce versions 2.4.4-p1 (and earlier) and 2.4.5 (and earlier) are affected by a Stored Cross-site Scripting vulnerability. Exploitation of this issue does not require user interaction and could result in a post-authentication arbitrary code execution.

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

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

6 open source packages ship an affected version, including magento/community-edition and magento/project-community-edition. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `magento/community-edition` | Packagist | All versions | None |
| `magento/community-edition` | Packagist | All versions | None |
| `magento/community-edition` | Packagist | From 2.4.3-p1 to 2.4.3-p3 | None |
| `magento/community-edition` | Packagist | From 2.4.3-p1 to 2.4.3-p3 | None |
| `magento/project-community-edition` | Packagist | All versions to 2.0.2 | None |
| `magento/project-community-edition` | Packagist | All versions to 2.0.2 | None |

Products: Adobe Commerce, Adobe Magento Open Source.

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

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

## Is CVE-2022-35698 being exploited?

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

Public exploit code:

- This repository contains potential security patches for the Magento APSB22-48 and CVE-2022-35698 security vulnerability (github_poc): https://github.com/EmicoEcommerce/Magento-APSB22-48-Security-Patches

## Other vulnerabilities in Adobe Commerce

- [CVE-2026-75650](https://insights.sbomify.com/CVE-2026-75650/): Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine (critical 10.0, exploited in the wild)
- [CVE-2024-34102](https://insights.sbomify.com/CVE-2024-34102/): Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) (critical 9.8, exploited in the wild)
- [CVE-2022-24086](https://insights.sbomify.com/CVE-2022-24086/): Adobe Commerce and Magento Open Source Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2026-48356](https://insights.sbomify.com/CVE-2026-48356/): Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type (critical 9.3, exploited in the wild)
- [CVE-2026-71362](https://insights.sbomify.com/CVE-2026-71362/): Adobe Commerce and Magento Incorrect Authorization Vulnerability (critical 9.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-35698 is a critical cross-site scripting vulnerability in Adobe Commerce, published on 14 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-35698 in the wild and no public exploit code.

Affected packages and fixed versions:
- magento/community-edition (Packagist): affected all versions; no fix listed
- magento/community-edition (Packagist): affected all versions; no fix listed
- magento/community-edition (Packagist): affected from 2.4.3-p1 up to 2.4.3-p3; no fix listed
- magento/community-edition (Packagist): affected from 2.4.3-p1 up to 2.4.3-p3; no fix listed
- magento/project-community-edition (Packagist): affected all versions up to 2.0.2; no fix listed
- magento/project-community-edition (Packagist): affected all versions up to 2.0.2; no fix listed

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-35698/ (Markdown: https://insights.sbomify.com/CVE-2022-35698/index.md)
```

## Sources

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

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