# CVE-2022-1916: Active Products Tables for WooCommerce < 1.0.5 - Reflected Cross-Site-Scripting

> Attackers can execute arbitrary scripts in users' browsers via unsanitized AJAX parameters in the Active Products Tables for WooCommerce plugin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5cf8-g57m-35gw

## What is CVE-2022-1916?

CVE-2022-1916 is a medium-severity cross-site scripting vulnerability in Unknown Active Products Tables for WooCommerce. Professional products tables for WooCommerce store, published on 27 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Active Products Tables for WooCommerce. Professional products tables for WooCommerce store WordPress plugin before 1.0.5 does not sanitise and escape a parameter before outputting it back in the response of an AJAX action (available to both unauthenticated and authenticated users), leading to a Reflected cross-Site Scripting

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

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

It affects 1 product.


Products: Pluginus Woot.

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

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

## Is CVE-2022-1916 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1916 exists.

Public exploit code:

- WordPress Active Products Tables for WooCommerce <1.0.5 - Cross-Site Scripting (nuclei): http/cves/2022/CVE-2022-1916.yaml

## Other vulnerabilities in Unknown Active Products Tables for WooCommerce. Professional products tables for WooCommerce store

- [CVE-2023-51505](https://insights.sbomify.com/CVE-2023-51505/): WordPress Active Products Tables for WooCommerce Plugin <= 1.0.6 is vulnerable to PHP Object Injection (critical 10.0)
- [CVE-2024-35730](https://insights.sbomify.com/CVE-2024-35730/): Cross-site scripting in Active Products Tables for WooCommerce (high 7.1)
- [CVE-2023-51480](https://insights.sbomify.com/CVE-2023-51480/): WordPress Active Products Tables for WooCommerce Plugin <= 1.0.6 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2024-10168](https://insights.sbomify.com/CVE-2024-10168/): Cross-site scripting in Active Products Tables for WooCommerce. Use constructor to create tables (medium 6.4)
- [CVE-2024-0796](https://insights.sbomify.com/CVE-2024-0796/): Cross-site request forgery in Active Products Tables for WooCommerce. Use constructor to create tables (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1916 is a medium-severity cross-site scripting vulnerability in Unknown Active Products Tables for WooCommerce. Professional products tables for WooCommerce store, published on 27 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1916 exists.

Affected product: Unknown Active Products Tables for WooCommerce. Professional products tables for WooCommerce store. 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-1916/ (Markdown: https://insights.sbomify.com/CVE-2022-1916/index.md)
```

## Sources

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

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