# CVE-2024-5324: XootiX Framework <= Various Plugin Versions - Missing Authorization to Arbitrary Options Update

> Authenticated subscribers can modify site options to enable registration and set default user roles to Administrator, leading to privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 6 Jun 2024
- **Updated:** 8 Apr 2026
- **Also known as:** CVE-2024-6721, GHSA-764x-99q3-75x3

## What is CVE-2024-5324?

CVE-2024-5324 is a high-severity missing authorization vulnerability in xootix Login & Register Customizer – Popup | Slider | Inline | WooCommerce, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple plugins for WordPress utilizing the XootiX Framework are vulnerable to unauthorized modification of data due to a missing capability check on the 'import_settings' function in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change arbitrary options on affected sites. This can be used to enable new user registration and set the default role for new users to Administrator.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

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

It affects 4 products.


Products: Xootix Login\/Signup Popup, Xootix Otp Login Woocommerce \& Gravity Forms, Xootix Side Cart Woocommerce, Xootix Waitlist Woocommerce.

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

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

## Is CVE-2024-5324 being exploited?

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

Public exploit code:

- Login/Signup Popup ( Inline Form + Woocommerce ) 2.7.1 - 2.7.2 - Missing Authorization to Arbitrary Options Update (github_poc): https://github.com/RandomRobbieBF/CVE-2024-5324

## Other vulnerabilities in xootix Login & Register Customizer – Popup | Slider | Inline | WooCommerce

- [CVE-2022-0215](https://insights.sbomify.com/CVE-2022-0215/): XootiX Plugins <= Various Versions Cross-Site Request Forgery to Arbitrary Options Update (high 8.8)
- [CVE-2020-36715](https://insights.sbomify.com/CVE-2020-36715/): Login/Signup Popup < 1.5 - Missing Authorization (high 7.4)
- [CVE-2025-1064](https://insights.sbomify.com/CVE-2025-1064/): Cross-site scripting in Login & Register Customizer – Popup | Slider | Inline | WooCommerce (medium 6.4)
- [CVE-2024-5665](https://insights.sbomify.com/CVE-2024-5665/): Login/Signup Popup ( Inline Form + Woocommerce ) 2.7.1 - 2.7.2 - Missing Authorization to Arbitrary Options Exposure (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5324 and fix it if it is affected.

What it is: CVE-2024-5324 is a high-severity missing authorization vulnerability in xootix Login & Register Customizer – Popup | Slider | Inline | WooCommerce, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5324 in the wild and no public exploit code.

Affected product: xootix Login & Register Customizer – Popup | Slider | Inline | WooCommerce. 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-5324/ (Markdown: https://insights.sbomify.com/CVE-2024-5324/index.md)
```

## Sources

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

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