# CVE-2022-0653: Profile Builder – User Profile & User Registration Forms <= 3.6.1 Reflected Cross-Site Scripting

> Attackers can inject arbitrary web scripts via the site_url parameter, executing code when users click crafted links.

- **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:** 24 Feb 2022
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-h98h-3vj4-grgq

## What is CVE-2022-0653?

CVE-2022-0653 is a medium-severity cross-site scripting vulnerability in Cozmoslabs Profile Builder – User Profile & User Registration Forms, published on 24 Feb 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 Profile Builder – User Profile & User Registration Forms WordPress plugin is vulnerable to Cross-Site Scripting due to insufficient escaping and sanitization of the site_url parameter found in the ~/assets/misc/fallback-page.php file which allows attackers to inject arbitrary web scripts onto a pages that executes whenever a user clicks on a specially crafted link by an attacker. This affects versions up to and including 3.6.1.

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

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

It affects 1 product.


Products: Cozmoslabs Profile Builder.

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

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

## Is CVE-2022-0653 being exploited?

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

Public exploit code:

- Wordpress Profile Builder Plugin Cross-Site Scripting (nuclei): http/cves/2022/CVE-2022-0653.yaml

## Other vulnerabilities in Cozmoslabs Profile Builder – User Profile & User Registration Forms

- [CVE-2024-6695](https://insights.sbomify.com/CVE-2024-6695/): profile-builder <= 3.11.8 - Unauthenticated Privilege Escalation (critical 9.8)
- [CVE-2023-2297](https://insights.sbomify.com/CVE-2023-2297/): Profile Builder – User Profile & User Registration Forms <= 3.9.0 - Insecure Password Reset Mechanism (critical 9.8)
- [CVE-2021-24527](https://insights.sbomify.com/CVE-2021-24527/): Profile Builder < 3.4.9 - Admin Access via Password Reset (critical 9.8)
- [CVE-2024-6366](https://insights.sbomify.com/CVE-2024-6366/): User Profile Builder < 3.11.8 - Unauthenticated Media Upload (critical 9.1)
- [CVE-2024-22140](https://insights.sbomify.com/CVE-2024-22140/): WordPress Profile Builder Pro Plugin <= 3.10.0 is vulnerable to Cross Site Request Forgery (CSRF) (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0653 is a medium-severity cross-site scripting vulnerability in Cozmoslabs Profile Builder – User Profile & User Registration Forms, published on 24 Feb 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-0653 exists.

Affected product: Cozmoslabs Profile Builder – User Profile & User Registration Forms. 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-0653/ (Markdown: https://insights.sbomify.com/CVE-2022-0653/index.md)
```

## Sources

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

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