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.
- 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
- None listed
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
Which versions are affected by CVE-2022-1051?
It affects 1 product.
Products include 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.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
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: 1 proofs of concept on GitHub.
Other vulnerabilities in Unknown WPQA Builder Plugin
- CVE-2024-2376 WPQA < 6.1.1 - Arbitrary Category and Tag Follow/Unfollow via CSRF
- CVE-2022-3688 WPQA < 5.9 - Follow/Unfollow via CSRF
- CVE-2022-1597 WPQA < 5.4 - Reflected Cross-Site Scripting
- CVE-2024-2375 WPQA < 6.1.1 - Contributor+ Stored XSS
- CVE-2022-1598 WPQA < 5.5 - Unauthenticated Private Message Disclosure
Sources
Also known as GHSA-p462-hx7j-6485.