# CVE-2022-1051: WPQA < 5.2 - Subscriber+ Stored Cross-Site Scripting via Profile fields

> Authenticated users can inject malicious scripts via profile fields in WPQA Builder, potentially leading to session hijacking or code execution.

- **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:** 16 May 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-p462-hx7j-6485

## What is CVE-2022-1051?

CVE-2022-1051 is a medium-severity cross-site scripting vulnerability in Unknown WPQA Builder Plugin, published on 16 May 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 WPQA Builder Plugin WordPress plugin before 5.2, used as a companion plugin for the Discy and Himer , does not sanitise and escape the city, phone or profile credentials fields when outputting it in the profile page, allowing any authenticated user to perform Cross-Site Scripting attacks.

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

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

It affects 1 product.


Products: 2code Wpqa Builder.

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

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

## Is CVE-2022-1051 being exploited?

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

Public exploit code:

- WPQA < 5.2 - Subscriber+ Stored Cross-Site Scripting via Profile fields (github_poc): https://github.com/V35HR4J/CVE-2022-1051

## Other vulnerabilities in Unknown WPQA Builder Plugin

- [CVE-2024-2376](https://insights.sbomify.com/CVE-2024-2376/): WPQA < 6.1.1 - Arbitrary Category and Tag Follow/Unfollow via CSRF (high 8.8)
- [CVE-2022-3688](https://insights.sbomify.com/CVE-2022-3688/): WPQA < 5.9 - Follow/Unfollow via CSRF (high 8.8)
- [CVE-2022-1597](https://insights.sbomify.com/CVE-2022-1597/): WPQA < 5.4 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2024-2375](https://insights.sbomify.com/CVE-2024-2375/): WPQA < 6.1.1 - Contributor+ Stored XSS (medium 5.9)
- [CVE-2022-1598](https://insights.sbomify.com/CVE-2022-1598/): WPQA < 5.5 - Unauthenticated Private Message Disclosure (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1051 is a medium-severity cross-site scripting vulnerability in Unknown WPQA Builder Plugin, published on 16 May 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-1051 in the wild and no public exploit code.

Affected product: Unknown WPQA Builder Plugin. 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-1051/ (Markdown: https://insights.sbomify.com/CVE-2022-1051/index.md)
```

## Sources

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

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