# CVE-2024-0324: Missing authorization in User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor

> Unauthenticated attackers can modify two-factor authentication settings for arbitrary user roles due to missing capability checks in the User Profile Builder plugin.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rv54-p5vw-c6p6

## What is CVE-2024-0324?

CVE-2024-0324 is a high-severity missing authorization vulnerability in cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wppb_two_factor_authentication_settings_update' function in all versions up to, and including, 3.10.8. This makes it possible for unauthenticated attackers to enable or disable the 2FA functionality present in the Premium version of the plugin for arbitrary user roles.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-0324?

It affects 1 product.


Products: Cozmoslabs Profile Builder.

## How do I fix CVE-2024-0324?

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

## Is CVE-2024-0324 being exploited?

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

Public exploit code:

- a PoC for CVE-2024-0324/WP Plugin - Profile Builder (<= 3.10.8) (github_poc): https://github.com/kodaichodai/CVE-2024-0324

## 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-2024-0324 and fix it if it is affected.

What it is: CVE-2024-0324 is a high-severity missing authorization vulnerability in cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0324 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-2024-0324/ (Markdown: https://insights.sbomify.com/CVE-2024-0324/index.md)
```

## Sources

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

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