# CVE-2022-2194: Accept Stripe Payments < 2.0.64 - Admin+ Stored Cross-Site Scripting

> Admin users can inject malicious scripts via unsanitized settings in the Accept Stripe Payments plugin, potentially compromising site integrity.

- **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:** 17 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8pf9-cjf8-hr4g

## What is CVE-2022-2194?

CVE-2022-2194 is a medium-severity cross-site scripting vulnerability in Unknown Accept Stripe Payments, published on 17 Jul 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Accept Stripe Payments WordPress plugin before 2.0.64 does not sanitize and escape some of its settings, allowing high privilege users such as admin to perform cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.

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

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

It affects 1 product.


Products: Tipsandtricks-Hq Accept Stripe.

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

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

## Is CVE-2022-2194 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2194 is a medium-severity cross-site scripting vulnerability in Unknown Accept Stripe Payments, published on 17 Jul 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-2194 in the wild and no public exploit code.

Affected product: Unknown Accept Stripe Payments. 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-2194/ (Markdown: https://insights.sbomify.com/CVE-2022-2194/index.md)
```

## Sources

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

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