# CVE-2021-25018: PPOM for WooCommerce < 24.0 - Subscriber+ Settings Update to Stored XSS

> Authenticated users can inject malicious scripts via settings due to missing authorization and sanitization, leading to stored XSS.

- **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:** 14 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gvfj-h2wq-cw77

## What is CVE-2021-25018?

CVE-2021-25018 is a medium-severity cross-site scripting vulnerability in Unknown PPOM for WooCommerce, published on 14 Feb 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 PPOM for WooCommerce WordPress plugin before 24.0 does not have authorisation and CSRF checks in the ppom_settings_panel_action AJAX action, allowing any authenticated to call it and set arbitrary settings. Furthermore, due to the lack of sanitisation and escaping, it could lead to Stored XSS issues

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2021-25018?

It affects 1 product.


Products: Najeebmedia Ppom for Woocommerce.

## How do I fix CVE-2021-25018?

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

## Is CVE-2021-25018 being exploited?

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

## Other vulnerabilities in Unknown PPOM for WooCommerce

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25018 and fix it if it is affected.

What it is: CVE-2021-25018 is a medium-severity cross-site scripting vulnerability in Unknown PPOM for WooCommerce, published on 14 Feb 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-2021-25018 in the wild and no public exploit code.

Affected product: Unknown PPOM for WooCommerce. 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-2021-25018/ (Markdown: https://insights.sbomify.com/CVE-2021-25018/index.md)
```

## Sources

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

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