# CVE-2021-42549: reflected XSS in search functionality of WP Cloud Plugins - Lets-Box

> Unauthenticated attackers can execute arbitrary scripts via reflected XSS in the Lets-Box WordPress plugin search functionality.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/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:** 13 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vvwh-jqqq-8v6c

## What is CVE-2021-42549?

CVE-2021-42549 is a medium-severity cross-site scripting vulnerability in WP Cloud Plugins Lets-Box, published on 13 Dec 2021. 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

Insufficient Input Validation in the search functionality of Wordpress plugin Lets-Box prior to 1.15.3 allows unauthenticated user to craft a reflected Cross-Site Scripting attack.

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

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

It affects 1 product.


Products: Wpcloudplugins Lets-Box.

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

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

## Is CVE-2021-42549 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-42549 is a medium-severity cross-site scripting vulnerability in WP Cloud Plugins Lets-Box, published on 13 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-42549 in the wild and no public exploit code.

Affected product: WP Cloud Plugins Lets-Box. 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-42549/ (Markdown: https://insights.sbomify.com/CVE-2021-42549/index.md)
```

## Sources

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

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