# CVE-2023-0814: Profile Builder – User Profile & User Registration Forms <= 3.9.0 - Sensitive Information Disclosure via Shortcode

> Authenticated subscribers can retrieve sensitive user meta data via a shortcode, potentially leading to high-privilege account takeover.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2pg6-wjcp-mmcq

## What is CVE-2023-0814?

CVE-2023-0814 is a medium-severity vulnerability in cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor, published on 14 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Profile Builder – User Profile & User Registration Forms plugin for WordPress is vulnerable to sensitive information disclosure via the [user_meta] shortcode in versions up to, and including 3.9.0. This is due to insufficient restriction on sensitive user meta values that can be called via that shortcode. This makes it possible for authenticated attackers, with subscriber-level permissions, and above to retrieve sensitive user meta that can be used to gain access to a high privileged user account. This does require the Usermeta shortcode be enabled to be exploited.

Weakness: CWE-863 (Incorrect Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-0814?

It affects 1 product.


Products: Cozmoslabs Profile Builder.

## How do I fix CVE-2023-0814?

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

## Is CVE-2023-0814 being exploited?

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

## Other vulnerabilities in cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor

- [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-2023-0814 and fix it if it is affected.

What it is: CVE-2023-0814 is a medium-severity vulnerability in cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor, published on 14 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-0814 in the wild and no public exploit code.

Affected product: cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor. 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-2023-0814/ (Markdown: https://insights.sbomify.com/CVE-2023-0814/index.md)
```

## Sources

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

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