# CVE-2024-4875: HT Mega – Absolute Addons For Elementor <= 2.5.2 - Missing Authorization to Options Update

> Authenticated subscribers can bypass authorization checks to update site options, potentially enabling unauthorized user registration.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 21 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hgvv-c4m6-65wv

## What is CVE-2024-4875?

CVE-2024-4875 is a medium-severity missing authorization vulnerability in devitemsllc HT Mega Addons for Elementor – Elementor Widgets & Template Builder, published on 21 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The HT Mega – Absolute Addons For Elementor plugin for WordPress is vulnerable to unauthorized modification of data|loss of data due to a missing capability check on the 'ajax_dismiss' function in versions up to, and including, 2.5.2. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to update options such as users_can_register, which can lead to unauthorized user registration.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Hasthemes Ht Mega.

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

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

## Is CVE-2024-4875 being exploited?

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

Public exploit code:

- HT Mega – Absolute Addons For Elementor <= 2.5.2 - Missing Authorization to Options Update (github_poc): https://github.com/RandomRobbieBF/CVE-2024-4875

## Other vulnerabilities in devitemsllc HT Mega Addons for Elementor – Elementor Widgets & Template Builder

- [CVE-2023-37999](https://insights.sbomify.com/CVE-2023-37999/): WordPress HT Mega Absolute Addons for Elementor plugin <= 2.2.0 - Unauthenticated Privilege Escalation vulnerability (critical 9.8)
- [CVE-2024-1974](https://insights.sbomify.com/CVE-2024-1974/): HT Mega – Absolute Addons For Elementor <= 2.4.5 - Authenticated (Contributor+) Directory Traversal (high 8.8)
- [CVE-2023-6214](https://insights.sbomify.com/CVE-2023-6214/): HT Mega – Absolute Addons For Elementor <= 2.4.6 - Sensitive Information Exposure via purchased_products (high 7.5)
- [CVE-2023-50901](https://insights.sbomify.com/CVE-2023-50901/): WordPress HT Mega Plugin <= 2.3.8 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2024-38706](https://insights.sbomify.com/CVE-2024-38706/): WordPress HT Mega plugin <= 2.5.7 - JSON Path Traversal vulnerability (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4875 is a medium-severity missing authorization vulnerability in devitemsllc HT Mega Addons for Elementor – Elementor Widgets & Template Builder, published on 21 May 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-4875 in the wild and no public exploit code.

Affected product: devitemsllc HT Mega Addons for Elementor – Elementor Widgets & Template Builder. 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-4875/ (Markdown: https://insights.sbomify.com/CVE-2024-4875/index.md)
```

## Sources

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

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