# CVE-2022-1818: Multi-page Toolkit <= 2.6 - Arbitrary Settings Update to Stored XSS via CSRF

> Attackers can force logged-in admins to update settings via CSRF, leading to stored XSS and potential code execution in the Multi-page Toolkit WordPress plugin.

- **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:** 20 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2xrf-hq77-g825

## What is CVE-2022-1818?

CVE-2022-1818 is a medium-severity vulnerability in Unknown Multi-page Toolkit, published on 20 Jun 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

The Multi-page Toolkit WordPress plugin through 2.6 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack and lead to Stored Cross-Site Scripting due to the lack of sanitisation and escaping as well

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Multi-Page Toolkit Project Multi-Page Toolkit.

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

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

## Is CVE-2022-1818 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1818 is a medium-severity vulnerability in Unknown Multi-page Toolkit, published on 20 Jun 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-1818 in the wild and no public exploit code.

Affected product: Unknown Multi-page Toolkit. 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-1818/ (Markdown: https://insights.sbomify.com/CVE-2022-1818/index.md)
```

## Sources

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

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